Context Navigation

Changes between Version 10 and Version 11 of Ticket #40428, comment 3

v10	v11
19	19
20	20	When creating features, please consider special needs users may be more likely to choose the browser which works best for their needs, and that browser may already have affordances built in to provide a better experience for them when assistive technologies like VO are enabled despite what standards bodies like W3C or WHATWG suggest.
21
22		~~----~~
23
24		I bring this up because I'm trying to refactor the `twentyseventeen_scripts` method in `functions.php` in Twenty Seventeen and am tripping all over `twentyseventeen_get_svg`, which seems to be an implicit time-based dependency on a theme file via use of the hooks system, and am being forced to give up affordances to accessibility as a result of the current design complexity.