angular.io
angular.io copied to clipboard
angular
Accessibility in examples
I logged #1147 about one issue already, and I see some really good WIP in the a11y cookbook, but I'm wondering, in general, what is the policy with regard to accessibility in the code samples outside of that cookbook? Is this something the project team has discussed? Overall, the docs are awesome, but I do feel like a11y is a weak point and TBH that's a little alarming given how influential this project is.
Any word on this? I don't mind contributing some PRs (or more issues), but I really think the project maintainers need to have a position on this subject.
FWIW, I would encourage a policy of accessibility by default. There's going to be a lot of developers who are basically learning to code from these docs, so I think the project has an obligation to promote techniques that support all users (I'd even argue that angular's own code of conduct mandates this). The a11y cookbook will be a great addition, but IMO if you have 99 docs demonstrating techniques that aren't friendly to users with disabilities, and 1 demonstrating techniques that are, there's still a problem. So I'd really like to see a project-level commitment to ensure some minimum level of accessibility across the board.
@wardbell I'll try to get some in fairly soon. I think the TOH app is the best place to start, but it seems like it appears over and over again, so there's a lot of ground to cover (plus I just need to get up to speed on the project structure and tooling and all that).
https://angular.io/features.html The features page says this: Accessibility
Create accessible applications with ARIA-enabled components, developer guides, and built-in a11y test infrastructure.
I have yet to find any of those details mentioned anywhere else on angular.io. Developer Guides - Don't seem to exist. Built-in a11y test infrastructure - no details on this.
For something that is highlighted on the features page, I would except some documentation on a11y.
