Archive index

A11y Slackers Gitter Channel Archive 18th of June 2016

What fresh hell is THIS now? - Patrick Lauke
  1. Sarbbottam Bandyopadhyay
    @sarbbottam
    Jun 18 03:50
    Hi there, I created this browser extention - Focus Indicator (chrome only as of now), to enhance browsing experience, when using keyboard, https://sarbbottam.github.io/accessibility,/javascript,/browser/extension/2016/06/17/focus-indicator-browser-extension … #accessibility
  2. Any feedback/concerns/suggestion is highly appreciated. Thanks!
  3. stevefaulkner
    @stevefaulkner
    Jun 18 06:31
    @jnurthen see you there (TPAC)
  4. Job van Achterberg
    @jkva
    Jun 18 10:09
    woop woop! role=drinks #3 in Amsterdam!
  5. Thierry Koblentz
    @thierryk
    Jun 18 15:14

    @sarbbottam there is no need to use display:inline-block on absolutely positioned elements.
    As a side note, why not plugging a simple rule instead of adding stuff to the DOM?
    Something like this may be?

    :focus {     outline: 3px solid teal !important; }
    

    My suggestion would be to create a page with the script so people can see/check how things work.

  6. Thierry Koblentz
    @thierryk
    Jun 18 15:37

    @MichielBijl in my opinion there are many reasons why we should avoid "tying CSS to DOM structure / elements”:

    • the DOM may change while the styling should stay the same
    • tying the styling to elements instead of classes changes the specificity scope (some stuff is styled via type, other via class, other is a mix of both, etc.). That creates more “specificity war” than using id (I’m serious)
    • in reality, if the project is anything else than a small project, the devs will have no other way than introducing classes to avoid styles collision. Either to overwrite what comes from the button rule or to add to the button rule. So better to start with the minimum styles for buttons (the job for a base style sheet) and use classes from there (to style that element within the same specificity scope).

    As a side note, Tim Baxter’s article demonstrates my first point as he uses <p> in a form thinking it is the only valid choice a dev would have [sic] and he also uses aria-expandedon the wrong node. Meaning the rules he wrote in that article would have to be re-written after he corrects the markup of his own examples.

  7. zakim-robot
    @zakim-robot
    Jun 18 18:55
    [nathanhammond] @marcysutton: Can we get eyes on this? dequelabs/axe-core#193
  8. Sarbbottam Bandyopadhyay
    @sarbbottam
    Jun 18 19:03
    Screen Shot 2016-06-18 at 11.55.16 AM.png
  9. Thanks @thierryk display-inline retained from continuous modification, thanks for pointing that. outline did not work for all the time, as suggested by you outline with -ve offset did work but impacts the readability
  10. Please see the above image. Thanks again!
  11. zakim-robot
    @zakim-robot
    Jun 18 19:05
    [marcysutton] @nathanhammond: noted, I will investigate when I'm back online!
  12. zakim-robot
    @zakim-robot
    Jun 18 19:19
    [marcysutton] More painting and removing some ugly-ass wallpaper is on the docket for this rainy day :umbrella:
  13. [nathanhammond] Pro tip on ugly wallpaper: remove it. :p