Meeting minutes
Minutes from last time, https://
https://
Derek and Bev introducing themselves to each other ...
Introductions
Progress updates
Welcome & Announcements (CEPC and IRC) to newcomers
See above -- we're now tracking from here, though!
Continuing progress on inventory of overlay facts, capabilities.html
We viewed the ability in iOS to label a button by the end user, at the edge
Derek: cant expect people on the edge to label things, that is against what we stand for
… but if it was a shared device, like a tablet, the ability to label on the advice would be very useful
… it is hard to tell people everything that inclusive design can bring, but if you use this strategy, you can achieve these things
janina: W3C can ask operating systems to do things.
… and WCAG has requirements regarding flashing. This should not be a guidance, it should be a requirement.
… this could be moved to the user-agent to prevent this blinking
Derek: Like Google Chrome enabled auto mute
derek: We have a list of capabilities that overlays can do
… what if we have a list of functionalities that the OS should never take away or block?
janina: Like some website disable the back button of the browser, so you cannot go back
… taking away 'alt-left'arrow' forces me to type out a URL
derek: At what level are we working? We seem to be zooming in and out, from technical details to high level 'in the clouds'
janina: We dont want advertising to be able to introduce a keyboard block.
… advertising is always an edge technology by definition, as the ad is served to the end-user's browser or app
Bev: I agree with the performance issues, and the general trend for more and more happening on the client side
… I am for end users having as much control as possible
janina: TO recap, if a user is worried about keyboard traps, or some kind of personal setting,
… set that concern in some technical way
… and tries to load a page with some kind of conformance level
… and an advertiser tries to push an advertisement that does not conform with the minimum conformance of the page
… the real time bid would be turned down
Bev: Exactly, if the end user can set their preferences in some way according to their needs or disability
derek: Do we want a role for 'ad's?
Lionel_Wolberger: will add advertising into capabilities
bev: wonders about warnings to users? should that be part of the path?
bev: sometimes we see those, but there's no reliability in the chain
Lionel_Wolberger: notes certificate errors on no https
Bev: The edge can provide warnings to users that there are flashing lights on the page
bev: thinking of warnings on flash
derek: text resizing, etc., picsels changing on screen
derek: could be just a few ms to evaluate
derek: notes google translate no longer in the header
Bev: It's not just epilepsy that is affected
derek: notes there will be populations that have adverse reactions to this
[group looks at branching to add content to our doc]
[discussion on how to do a good, fully cross-referenced pull request]
[discussion on what's appropriate under redundancy]
sometimes ok, sometimes not
derek: if it augments, it's probably ok
derek: There's times where redundancy is appropriate because it augments functionality rerather than only replicating
derek: as opposed to just replicate
derek: TTS generated might have pronunciation support that enhances
… readspeaker for example has a role with cognitive disabilities and neurodiversity who appreciate the redundancy
Bev: Not to limit the capacity for tuning.
bev: don't limit the ability to fine tune
Bev: we should do everything in our power to allow the user to tune to their needs