Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: screen reader helper/visibility utility tweaks #31133

Merged
merged 7 commits into from
Jul 10, 2020
Merged

Conversation

patrickhlauke
Copy link
Member

  • rename "Screen readers" helper to "Visually hidden" (in future, may consider actually renaming the classes as well? .visually-hidden / .visually-hidden-focusable or similar?)
  • reword description for visibility utility, emphasise/call out the fact that .invisible hides stuff from AT

@patrickhlauke
Copy link
Member Author

meta-question: what's the cut-off between something being a "helper" and something being a "utility"?

patrickhlauke added a commit that referenced this pull request Jun 21, 2020
To be more representative of the fact that these are not necessarily "screen reader" specific, but actually apply to assistive technologies in general (and also things like Alexa/Siri/etc). Goes hand-in-hand with #31133
@patrickhlauke
Copy link
Member Author

Related, the proposed PR to actually rename the classes/mixins as well #31139

@XhmikosR
Copy link
Member

Note that we should focus to v5 and leave v4 in maintenance mode. We don't need to backport everything. Also, this needs to be handled carefully in v4 with a redirect.

@patrickhlauke
Copy link
Member Author

ok, there's probably little point in backporting just this bit. focusing on v5 makes sense.

@patrickhlauke
Copy link
Member Author

@XhmikosR should this also have an aliases?

@XhmikosR
Copy link
Member

@XhmikosR should this also have an aliases?

Doesn't hurt but maybe we don't need to, since it's still an alpha. I'll add a note to revisit the aliases later.

XhmikosR added a commit that referenced this pull request Jul 3, 2020
* Rename `sr-only`/`sr-only-focusable`

To be more representative of the fact that these are not necessarily "screen reader" specific, but actually apply to assistive technologies in general (and also things like Alexa/Siri/etc). Goes hand-in-hand with #31133

Co-authored-by: XhmikosR <[email protected]>
"screen readers" is quite reductive, as there are other assistive technologies. content hidden this way is even announced by things like Alexa/Siri etc, so it's not so much just "screen readers".
in the long run, we may even consider changing the actual classnames (maybe `.visually-hidden` / `.visually-hidden-focusable`, though admittedly that's a bit verbose).

also includes a tiny tweak to layout.md to generalise the note about using `.sr-only`
@mdo
Copy link
Member

mdo commented Jul 6, 2020

meta-question: what's the cut-off between something being a "helper" and something being a "utility"?

Generally speaking, utilities are single property-value pairings and helpers are shortcuts or snippets.

@patrickhlauke
Copy link
Member Author

any chance of a review please? ;)

Copy link
Member

@XhmikosR XhmikosR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM but I want @mdo to also review

Copy link
Member

@ffoodd ffoodd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@patrickhlauke patrickhlauke requested a review from mdo July 6, 2020 11:27
@mdo mdo merged commit 69b3c46 into main Jul 10, 2020
@mdo mdo deleted the v5-docs-sr-visibility branch July 10, 2020 23:00
olsza pushed a commit to olsza/bootstrap that referenced this pull request Oct 3, 2020
* Rename `sr-only`/`sr-only-focusable`

To be more representative of the fact that these are not necessarily "screen reader" specific, but actually apply to assistive technologies in general (and also things like Alexa/Siri/etc). Goes hand-in-hand with twbs#31133

Co-authored-by: XhmikosR <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants