Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Borges

fat
May 21, 2012

 Borges

JSConf.AR 2012 - Who is Jorge Luis Borges and why would you talk about him at a JavaScript conference?

fat

May 21, 2012
Tweet

More Decks by fat

Other Decks in Technology

Transcript

  1. @fat
    May 2012
    Jorge Luis Borges

    View full-size slide

  2. I work at twitter

    View full-size slide

  3. I write libraries

    View full-size slide

  4. Bootstrap Hogan.js Ender

    View full-size slide

  5. I even read real books from real libraries sometimes

    View full-size slide

  6. I’ve made it a point to talk about books

    View full-size slide

  7. We’re in ARGENTINA

    View full-size slide

  8. Jorge Luis Borges

    View full-size slide

  9. But what should I really talk about?

    View full-size slide

  10. 1899 Jorge Francisco Isidoro Luis Borges Acevedo

    View full-size slide

  11. Primarily educated by his parents and english grandmother

    View full-size slide

  12. Translated The Happy Prince by Oscar Wilde at 9 years old

    View full-size slide

  13. His family moves around Europe a lot, trying to evade the war

    View full-size slide

  14. Ultraísmo the avante-garde, anti-modernist movement

    View full-size slide

  15. 1921 Borges returns to Argentina

    View full-size slide

  16. Just two years later he publishes his first book of poems

    View full-size slide

  17. He continues to publish new works every 2-3 years

    View full-size slide

  18. 1937 father falls ill and Borges takes up first full time job

    View full-size slide

  19. First assistant for a small branch of the municipal library

    View full-size slide

  20. 9 years he hates it

    View full-size slide

  21. Hides in the basement writes a bunch

    View full-size slide

  22. Perón gains power and Borges is promoted to a new position as
    an agricultural inspector

    View full-size slide

  23. Declines and accepts work as a lecturer of English literature

    View full-size slide

  24. After Perón and Borges named Director of National Library

    View full-size slide

  25. The same year doctor informs him that he’s too blind to ever read
    or write on his own again

    View full-size slide

  26. No one should read self-pity or reproach
    into this statement of the majesty
    of God, who with such splendid irony
    granted me books and blindness in one touch.
    Borges Poem of the Gifts

    View full-size slide

  27. As I read this, I began to think about our Libraries

    View full-size slide

  28. How many would actually be accessible by Borges?

    View full-size slide

  29. So I went to Github

    View full-size slide

  30. And I sampled the top 15 UI libraries with 1500+ watchers

    View full-size slide

  31. Bootstrap, impress.js, chosen, jquery-file-upload, jquery-ui,
    spin.js, deck.js, Skeleton, Foundation, showoff, file-uploader,
    isotope, timeline, etherpad-lite, colorbox

    View full-size slide

  32. Of 15 libraries only one was optimised for accessibility

    View full-size slide

  33. it wasn’t Bootstrap

    View full-size slide

  34. Clearly, I know nothing about accessibility

    View full-size slide

  35. I had heard of ARIA, I knew there were some specs

    View full-size slide

  36. So I started to ask, “What is this accessibility thing anyways?”

    View full-size slide

  37. So I started digging through the W3C

    View full-size slide

  38. Later I find out the bro in the photo is Daniel Dardailler

    View full-size slide

  39. Around Fall 96’ Web Accessibility Initiative is “conceived”

    View full-size slide

  40. Official press release for WAI ~9 months later

    View full-size slide

  41. Remember, this is 1996

    View full-size slide

  42. January 1997 the W3C releases HTML 3.2

    View full-size slide

  43. By then CSS 1.0 had been around for about a year

    View full-size slide

  44. Despite this, WYSIWYGs doing crazy WYSIWYG s**t

    View full-size slide

  45. No alt, presentational attrs, incorrect H1’s, blockquote, font tags

    View full-size slide

  46. Other insane techniques also pop up like Frames for templating

    View full-size slide

  47. Dec 97’ we find the first notes on accessibility in HTML 4.0

    View full-size slide

  48. Oh Hai semantic markup, doc structure, title, lang, and more

    View full-size slide

  49. Meanwhile WYSIWYGs are still WYSIWYGing and getting worse

    View full-size slide

  50. Finally in 99’ Web Content Accessibility Guidelines (WCAG) 1.0

    View full-size slide

  51. This was the first set of international guidelines developed by
    the W3C Web Accessibility Initiative (WAI) with the intent of
    providing information for web developers to create accessible
    web content

    View full-size slide

  52. Surely this will save the web

    View full-size slide

  53. Nope WYSIWYGs gonna WYSIWYG

    View full-size slide

  54. W3C release the Authoring Tools Accessibility Guidelines
    (ATAG) 1.0, and HTML 4.01

    View full-size slide

  55. MS Frontpage and Dreamweaver say “Cool Story Bro”

    View full-size slide

  56. Some developers are starting to get the idea

    View full-size slide

  57. But they’re forced to use external plugins like HTML tidy

    View full-size slide

  58. These people were considered “Pioneers”

    View full-size slide

  59. CMS gains popularity, even more sad times

    View full-size slide

  60. Sep 2000 the WAI try again with WCAG 2.0

    View full-size slide

  61. 6 years later the WAI announce it’s final working draft

    View full-size slide

  62. People go full internet and write “To Hell with WCAG 2”

    View full-size slide

  63. Developers hoping for “Accessibility for the real world”

    View full-size slide

  64. This same year WAI releases the first working draft for the
    Roadmap for Accessible Rich Internet Applications

    View full-size slide

  65. Specific to Web content and Web applications \o/

    View full-size slide

  66. Roles and Implementation Guides

    View full-size slide

  67. This is where we are today and it’s not that bad

    View full-size slide

  68. So how do I close issue #931?

    View full-size slide

  69. How do I do my part to reach every person on the planet?

    View full-size slide

  70. Easy i just close it

    View full-size slide

  71. Reopen 10 new tickets One for each interactive component

    View full-size slide

  72. Use tickets to draft implementation details around Accessibility

    View full-size slide

  73. Use Aria’s “12 General Steps for Building an Accessible Widget”

    View full-size slide

  74. Reach out to specialists and organize hackathons

    View full-size slide

  75. Jacob @fat
    poll: If we provided food, drink, and twitter office,
    would you be interested in coming in to hack on
    bootstrap accessibility w/ @mdo and I?

    View full-size slide

  76. and then just... try to do stuff

    View full-size slide

  77. In just 3 days I’ve dramatically improved accessibility

    View full-size slide

  78. Dialogs now limit focus to active area

    View full-size slide

  79. Dropdowns now support keyboard navigation

    View full-size slide

  80. Tabs are now focusable widget areas

    View full-size slide

  81. I’ve added aria roles to dialogs, buttons, toolbars, and more

    View full-size slide

  82. But maybe most importantly I’ve talked to you about accessiblity

    View full-size slide

  83. follow @fakeangus

    View full-size slide