On 5/23/2020 8:52 AM, Stephen J. Turnbull wrote: > Executive summary: > > I'd like to make three points. > > 1. Accessibility matters, and I think this change would be > inaccessible to users of screen readers. > 2. Yes, a variety of tools imposes a burden, but also confers > benefits. > 3. There's no such thing as "pretty source code." There are only > tools that display source code beautifully. > > Down and dirty details: > > The first is new to this discussion: > > Let's not make life more annoying for the accessibility developers and > the people who *need* accessibility accommodations. Not all visual > puns are audible puns. "→" looks like "->", but "Unicode U+2192 > RIGHTWARDS ARROW" sounds nothing like "HYPHEN GREATER-THAN". (I'm > guessing at the pronunciation, I don't use a screen reader myself. > OK, probably the reader just says "RIGHTWARDS ARROW" or even > "RIGHTARROW", but it's still not close to the same.) Microsoft Narrator totally skips → when I got it to read the subject line on this email (Result: "I'd like to suggest allowing unicode as an alternative to 'dash'"). There might be other screen readers that work better, but I agree that this would increase inaccessibility.
--Edwin _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/2SZG2GVHGTMVPDZXFWWC6D2VVSZZ7XBP/ Code of Conduct: http://python.org/psf/codeofconduct/
