question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Docs] New page for generic accessibility classes and attributes

See original GitHub issue

Prerequisites

Proposal

There are quite a number of pages in the docs which discuss accessibility.

It would be very helpful to have a new “accessibility” page which summarises all generic accessibility classes / aria attributes in one place. I’m not referring to accessibility specific to some component, but rather those bits that are generic.

For example, I always struggle to remember how to show visually and hide to screen readers, or vice versa (aria-hidden="true" and .visually-hidden). One of those has a dedicated page, and the other does not.

Motivation and context

I refer to the docs regularly. And I always find it difficult to find the bit that I’m looking for - I can’t remember if it’s under the “text”, “reboot”, “visibility”, “visually hidden”, etc., pages.

Issue Analytics

  • State:open
  • Created 9 months ago
  • Reactions:2
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
lonix1commented, Dec 8, 2022

@julien-deramond LOL, you see that’s what I’m talking about. I forgot about that page completely! 😄

I was initially thinking of a small dedicated page in the “utilities” section. But the one you’ve linked to is good; maybe it could be expanded. But then the overlapping bits on other pages might need to be moved.

Basically, all the info already exists in the docs right now, but in a number of different places.

1reaction
julien-deramondcommented, Dec 8, 2022

Yes some info about a11y is very generic (global classes, our philosophy, etc.), some is very specific to one component and will depend on the context of the use of one component. But I understand the point. I haven’t checked everything but in the other pages, maybe we can link when possible to this main Accessibility page so that the users are used to go there, and try to gather in this main page most of the info. Let’s try something 😃 Thanks for the feedback btw!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Make your document or presentation more accessible
When you create a document or presentation, follow the tips below to make it more readable by everyone, including people with disabilities.
Read more >
HTML: A good basis for accessibility - Learn web development
You should now be well-versed in writing accessible HTML for most occasions. Our WAI-ARIA basics article will help to fill gaps in this ......
Read more >
Generic Classes - C# Programming Guide - Microsoft Learn
Learn about generic classes used in collections like linked lists, ... especially regarding inheritance and member accessibility.
Read more >
Links - Usability & Web Accessibility - Yale University
Download the Link Accessibility for Content Editors training slides. ... While screen readers can read a full page to a user, screen reader...
Read more >
WebView - Android Developers
android:accessibilityLiveRegion, Indicates to accessibility services ... Returns a new set of layout parameters based on the supplied attributes set.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found