Explore >> Select a destination
|
You are here 
|
hidde.blog | ||
| | | | |
hiddedevries.nl
|
|
| | | | | Hidde's blog about web accessibility, standards, HTML, CSS, JavaScript and more. | |
| | | | |
www.smashingmagazine.com
|
|
| | | | | Successful web accessibility is about anticipating the different needs of all sorts of people, understanding your fellow web users and the different ways they consume information. Armed with this understanding, accessibility becomes a cold, hard technical challenge. How do assistive technologies present a web application to make it accessible for their users? Where do they get the information they need?One of the keys is a technology known as the accessibility API. | |
| | | | |
hiredigitally.com
|
|
| | | | | [AI summary] The article discusses how to improve the accessibility of single-page applications (SPAs) by using semantic HTML, proper form elements, and other best practices. | |
| | | | |
www.unindented.org
|
|
| | | I was reading MDN's article on signaling and video calling, and encountered this part: WebRTC is a fully peer-to-peer technology for the real-time exchange of audio, video, and data, with one central caveat. A form of discovery and media format negotiation must take place, as discussed elsewhere, in order for two devices on different networks to locate one another. This process is called signaling and involves both devices connecting to a third, mutually agreed-upon server. Through this third server, the two devices can locate one another, and exchange negotiation messages. It then goes on to talk about SDP, the protocol used to exchange signaling information, and guides you through implementing a video-calling app. I started wondering, do you really need th... | ||
