What does starting much higher up in the PUA chain means? PUA is PUA right?
On Tue, Sep 9, 2014 at 2:30 PM, Shahyar Ghobadpour < [email protected]> wrote: > We can avoid the PUA areas that are commonly used for emoji, and start > much higher up the PUA chain. That's the best we can do, and should work > for pretty much everything. > > --Shahyar > > On Mon, Aug 25, 2014 at 5:35 PM, Matthew Flaschen <[email protected] > > wrote: > >> On 08/22/2014 02:17 PM, Shahyar Ghobadpour wrote: >> >>> I'm chiming in late here, but our icons are in the PUA, and therefore >>> have nothing to actually "read". aria-hidden is not necessary in this >>> scenario; it is only needed when you are using unicode characters that >>> can be read by a screen reader as something (eg. the caret glyph is read >>> as "n-ary logical and"), but don't want it to because it is ornamental. >>> >> >> One potential issue they discuss for PUA is: >> >> "Using the PUA avoids semantic conflicts, but that still leaves us with >> visual ones. For example, some operating system default fonts define their >> own characters in the PUA. If any of your icons are mapped to a character >> with a default glyph and the font request doesn’t successfully complete, >> the default glyph will be shown." >> >> I don't know how real an issue this is (they discuss an apparent >> real-world example on iOS). Might there be a noticeable number of failed >> font requests on mobile? Are we avoiding the no-go areas of the PUA? >> >> >> Matt Flaschen >> >> >> _______________________________________________ >> Design mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/design >> > > > _______________________________________________ > Design mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/design > >
_______________________________________________ Design mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/design
