Meeting minutes
TOPIC new spreadsheet
https://
<jjdg> TOPIC https://
JJ: the whole thing will be open source
JJ: Appt Beta Info highlights – more than 10% of people use two or more devices
JJ: Disabilities versus abilities versus permanent or situational
JJ: more information in futures. Android and iOS next to each other to compare. Most settings are available in both platforms
JJ: iOS audio settings – differences in iOS/android captions use, same with dark mode – Looking into reasons. Seeing how deeply in the settings these are
JJ: data collection, analytics is already open source. Haven't received any negative messages about data collection.
JJ: there's an API reference, Still building. Shows properties that are inherited. Looking for feedback from developers on this
JJ: I've been spending most of my time include samples – 22, available for all platforms. These are linked to success criteria. Drop-down lets you switch platforms.
JJ: all the code samples are on the left see see them at once. There will be more. Are we going to do deeper on some platforms – still figuring out
JJ: all three guidelines EN and Section 508
JJ: still hard to know exactly what you need to do, but this is a first pass. Summary, impact, check, solution, sometimes example, support for video. Pick your programming language and go to all of the guidelines and see how to implement.
JJ: 22 code samples but not all of them have been embedded
JJ: we have documentation on disabilities, still working on, assistive technologies for using apps – in-depth articles. For instance outback has a large page all the gestures, videos, Keyboard access we have all the keyboard commands.
JJ: In-depth articles so people learn how to use the excessive technologies. It's also available in Dutch.
JJ: looking for more partners
JJ: also looking for authors for articles
JJ: October we are testing get feedback and
Mick: super impressive.
+1
JJ: we been getting good responses – mostly on slack and twitter
JJ: 5000 Page views in the first four days
Mick: having that quick action to flip Between libraries is really useful. Have the guidelines broken down – three different types is really helpful. It's a great Go to. It does seem more developer focus but there's more out there for design.
JJ: at first we were considering multiple groups – designers, even product owners but we shifted to developers because we have all these code samples. It does change how you write the articles. It's a little different how a developer uses talkback as opposed to a designer or manager. Maybe in the future more documentation.
JJ: That's something we are figuring out. We are adding some interviews as well. People with disabilities and how they use their phone – what kind of settings they use. I think there should also be video.
JJ: People – why they are doing this, how It helps them
Mick: Asking about the name
JJ: makes sense in Dutch – everyone should be able to use
JJ: we plan to do audits and embed the code examples inside our reports – this is something other companies can do – companies can request access, API
<jjdg> Kim: explains 2.1 Keyboard background - Indie UI
WCAG 2.2 new succes criteria
<jjdg> Why Section 508 and EN 301 549 exclude 3.2.3 Consistent Navigation and 3.2.4 Consistent Identification
<jjdg> Gaps because it's hard to test
Next meeting next week