aria-practices

WAI-ARIA Authoring Practices Guide (APG) (by w3c)

Aria-practices Alternatives

Similar projects and alternatives to aria-practices

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better aria-practices alternative or higher similarity.

aria-practices reviews and mentions

Posts with mentions or reviews of aria-practices. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-13.
  • Here are the 10 projects I am contributing to over the next 6 months. Share yours
    13 projects | dev.to | 13 Apr 2024
    W3C Aria Practices
  • React Arborist – A full-featured tree component for React
    7 projects | news.ycombinator.com | 21 Mar 2022
    I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility?

    W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are:

    https://w3c.github.io/aria-practices/#TreeView

    https://w3c.github.io/aria-practices/examples/treeview/treev...

    I ask because I've tried to implement a [TreeGrid](https://w3c.github.io/aria-practices/#treegrid) myself before and... it's a lot of work. I'd love an accessible, keyboard-friendly React tree :).

  • Custom JavaScript controls can't capture the nuance of form fields (2021)
    4 projects | news.ycombinator.com | 24 Feb 2022
    Yep I totally agree with this.

    There are however a bunch of ARIA tags & best practices etc (https://w3c.github.io/aria-practices/) that exist to make popups and dialogs (and other things e.g. tree views or "email-inbox-style" "treegrids" etc) accessible (if implemented correctly).

    I am conflicted about these - it is nice that there are ARIA tags for this, but it would also be nice if browsers "understood" aria tags and added some default behaviors (e.g. keyboard navigation). As it is, ARIA tags are essentially "pointless" to anyone who doesn't use an assistive technology, and so non-assitive-technology users nor developers benefit from using ARIA tags so they are often forgotten. If the browsers saw that there was an A11y-tree that matched a treeview or a treegrid, it would be really really nice if they applied some default common keyboard navigation implementation, rather than do nothing and leave it up to the developer to decide what keys do what on each and every site. .... Or on the other hand, is that too prescriptive and should we give developers and UX designers more leeway to design something better, rather than rely on browser-enforced defaults? I guess we are happy with browser defaults for basic inputs, but would we be for a treegrid?

  • 4 takeaways from axe-con 2021
    2 projects | dev.to | 29 Mar 2021
    The ARIA practices GitHub is a good resource to see where certain patterns fall short.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 1 May 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic aria-practices repo stats
4
1,159
8.0
1 day ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com