[Accessibility] Incorporate Advanced Settings Warning into Screen Reader Flow

[aphelionz]

We should find a way to incorporate this warning (at least the warning header) into the screen reader flow.

Also, interesting note: There's actually something in the disability community called "The Dignity of Risk" which states that people with disabilities should be allowed to take risks and endanger themselves in the same banal ways that others do. http://www.disabilitypracticeinstitute.com/services/“dignity-of-risk”/

If we can break stuff, they can break stuff too! It's only fair (but they should know the warnings)

[cjcenizal]

@aphelionz "Dignity of risk". I ❤️ this. I think this principle can be extrapolated to all users too. Very often, we're tempted to treat our users like toddlers and put up guardrails by eliminating choices or hiding information because we're afraid of the user making a "bad" choice. But I think we need to take the opposite approach: fully inform the user about the choices they can make, set expectations appropriately, and then let them make bad choices if they desire.

[chrisronline]

This doesn't seem trivial. Moving to phase 2

[timroes]

@aphelionz could you shortly explain, why it isn't in the screen reader flow? From what I tested, switching to advanced settings doesn't set your focus somewhere behind the warning, so the screen reader should just come over that warning, before it hits any search box or settings. We could additionally aria-describedby the search input with the warning heading "Caution: You can break stuff here".

[aphelionz]

@timroes Adding the aria-describedby is fine, and really all I was getting it. This is much simpler than the discussion made it seem :)