This is still very draft and prototype only.

• Add CSS styling for .at-guidance sections with visual distinction
• Implement comprehensive AT guidance for suggestion role with screen reader recommendations
• Add AT guidance for slider role covering screen readers, voice control, and switch navigation
• Add AT guidance for aria-expanded state with platform-specific implementation details
• Add editorial documentation to README.md explaining when and how to add AT guidance
• Use proper h5/h6 heading hierarchy for AT guidance sections
• Include RFC 2119 compliant language (MUST, SHOULD, MAY) for normative guidance
• Provide concrete examples and focus on user benefits for each AT guidance section

Closes #????

Describe Change Here!

And a few other todo items (delete this section after performing them):

• For every spec that this PR edits, please add the appropriatespec:<spec_name> label. If you don't have privileges to do this, editors will do it for you.
• If the change iseditorial, please add "Editorial:" at the start of your PR name, and delete the "Test, Documentation and Implementation tracking" section below.

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

• "author MUST" tests:
• "user agent MUST" tests:
• Browser implementations (link to issue or commit):
  • WebKit:
  • Gecko:
  • Blink:
• ACT review?
• Does this need AT implementations?
• Related APG Issue/PR:
• MDN Issue/PR:

Preview |Diff