Skip to content

[flexbox] Confusing sentence in a note about order and navigation #1677

Closed

Description

@frivoal

The following sentence (the last one in section 5.4.1. Reordering and Accessibility in flexbox) is problematic:

However a UA that uses order in determining sequential navigation, but does not otherwise account for spatial relationships among elements (as expressed by the various layout features of CSS including and not limited to flex layout), is non-conforming.

It looks like it is trying to introduce a conformance requirement in a note, which is not OK.

What is is actually trying to do is to illustrate a way than an implementation could fail to honor the normative conformance requirement already introduced by the second sentence of the section:

Likewise, order does not affect the default traversal order of sequential navigation modes (such as cycling through links, see e.g. tabindex [HTML5]).

Activity

  1. astearns commented on Aug 3, 2017

    @astearns
    Member

    Since the conformance requirement already exists, I'm not sure the example in the note needs to reinforce it. What if we changed the sentence in the note to something like:

    But order is not the only (or even the first) CSS property that would need to be considered for a spatial navigation feature. A well-implemented spatial navigation feature would need to consider all the layout features of CSS that modify spatial relationships.

  2. fantasai commented on Aug 3, 2017

    @fantasai
    Collaborator

    Works for me. Did you mean first as in "earliest defined" or first as in "primary"?

  3. astearns commented on Aug 3, 2017

    @astearns
    Member

    I meant primary, but I suppose it works either way.

  4. fantasai commented on Aug 4, 2017

    @fantasai
    Collaborator

    In that case I'll s/first/primary/. :)

  5. tantek commented on Aug 4, 2017

    @tantek
    Contributor

    Alan's proposed changed sentence is an improvement, with either first/primary (editor discretion). LGTM.

  6. added this to the milestone on Mar 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions