Ioana Chiorean

The web is pretty much present in everyone's life nowdays. But is it really for all? How are we making it a smooth usage for those with disabilities, for those with reduce time and internet connection? Or even more further, for those that just use the web for the first time? Let's learn a bit how the devtools from Firefox can help us improve everyone's experience without much of a sacrifice on our end.

A11y and inclusion is getting more traction nowadays but people still think that they address only those with disabilities. As a person without any officially i did find myself in this situation and felt confused about how the web should be ( was about to loose money on ticket conferences because i was not seeing the categories). Some Developers are a bit defensive saying they don't have users for whom to build more a11y in or the time to add these features. Showing the devtools Firefox has for it - will show how fast you can check your page and how no costy is. Also not knowing all best practices won't be a blocker and firefox will give you suggestions. In a way i wanted to bring attention to A11y nd Inclusion in a more technical way.

Many developers do not consider web standards while create their webpages/apps. This will create a bad experience for some users that not use that product with a certain OS or application. This talk will cover best practices and give examples of how some users could not do some simple booking because of the bad experience given by the website for their app. This will cover web in general, not only Firefox.

Many developers do not consider web standards while create their webpages/apps. This will create a bad experience for some users that not use that product with a certain OS or application. And nowdays there are way to many configuration available to be sure you use the right one. And a limited memory will narrow your option to have several apps installed only for certain webpages. Some simple example for a bike sharing system, a Michelin rated restaurant from Stockholm or a museum in Krakow - that worked poorly on several browsers will show the importance of compatibility. Best practices for developers will be presented. Best practices for report issues will be exemplified. Already fixed issue will present simple solutions to the audience that unblocked several users.

In our efforts to build Firefox OS and Firefox for Android as solutions for Mobile World we don't have any control of the web content available out there. We can build up a better user experience but the products will still be afffected by the lack of standards. As stock browsers (both iPhone and Android) are build upon Webkit rendering engine. other browsers (including Firefox for Android) will experience top sites returning desktop content, inferior mobile sites, or sites with broken layout and functionality.