Showing posts with label browsers. Show all posts
Showing posts with label browsers. Show all posts

Saturday, May 10, 2025

POUR - WCAG

The Web Content Accessibility Guidelines (WCAG), developed by the World Wide Web Consortium, are technical standards that help make the digital world accessible to people with disabilities. WCAG standards are rooted in four main principles: perceivable, operable, understandable, and robust, often called POUR.

Perceivable

Information must be perceivable to people using only one of their senses, so they understand all related content.

My thots: Check the contrast outside under bright lighting conditions. Ensure the audio understandable in a noisy room. Both light and dark backgrounds are common, ensure text color adjusts. There are various forms of color-blindness, check using a color-blind simulator and/or in grayscale to ensure no meaningful information is lost--that is, a red circle and a green circle are the same when the color is muted. Wear hearing protection to ensure alternatives to increasing the volume are available when possible. Blur your vision (or remove your glasses) to ensure the text and image size can be increased to improve readability. Ensure temporary notifications display sufficiently long to be recognized when distracted. Display on a large projected image (where color and contrast may vary).

Operable

End users must be able to interact with all webpage elements. For instance, your website should be easily navigable with just a keyboard or voice controls for non-mouse users.

My thots: Wear gloves, thus causing a loss of precise touch. Use just a keyboard--don't rely on a mouse cursor. Use just a touch-screen--don't rely on hover-text. Use a small screen (e.g., mobile phone). Use a connected display some distance away with just a mouse, for example, use a wide-screen TV and a mouse on an uneven surface or a TV remote.

Understandable

The principle is just what it seems—end users must be able to understand web page content and functionality information.

My thots: this principle should be true for all means of communication, but it is very difficult especially given the diversity of the audience. Those who don't know English are left with machine translation. As a person with an analytical, engineering mind, I find that most web sites do a very poor job with understandability for me because their audience is primarily non-technical, emotionally driven, neurotypical people. If I don't already know what a company does, visiting their website seldom gives me more than just a clue about what they do. For example, take this headline, "Essential Software - For the People Who Change the World." OK, at least I know it's a software company, but what kind and is it cloud-based, mobile, desktop, a framework to be integrated, self-service or requires technical professional consultants to configure? The next subheading helps: "Software built for fundraising, nonprofit accounting, education, CSR and more." Now, I know what markets this software is design to meet. There's a financial component and an educational component and CSR, whatever that is--though if I don't know what CSR means, this software is probably not what I need. But then the subheading continues with "Fueling bigger, bolder impact — everywhere." What does that mean? 

Robust

Your website must effectively communicate information to all users, including users of assistive technologies, and remain compatible with evolving technologies and user needs.

My thots: let's face, this is a goal seldom reached because of expense and lack of knowledge of capabilities. Also, not everything needs to be accessible, at least not on a practical level. For example, a website to sell a product that requires sight to use has little need for a website compatible with those who can't see. Technology has advanced making some best practices no longer important. For example, using relative styles (i.e., not "pt") for font size is not nearly as important now that browsers allow the magnification of the entire screen to scale. 

My biggest fight has been with web page designers who want to control the appearance of the page and not allow the viewer to decide how they want to interact with the content.

source: https://www.wcag.com/resource/what-is-wcag/

Friday, January 21, 2022

Post/Redirect/Get (PRG)

Post/Redirect/Get (PRG) is a web development design pattern that lets the page shown after a form submission be reloaded without submitting the form another time. Some browsers mitigate this risk by warning the user that they are about to re-issue a POST request.

To avoid this problem, many web developers use the PRG pattern—instead of responding with content, the server responds to a POST request by redirecting the client to another location. The HTTP 303 See Other response code to cause the browser to REDIRECT and GET a new page.

The PRG pattern cannot address every scenario of duplicate form submission. For example, if a web user refreshes before the initial submission completes, possibly because of server lag, a duplicate POST occurs in certain user agents.

Source: http://en.wikipedia.org/wiki/Post/Redirect/Get 2022-01-18

Sunday, August 12, 2018

Content-Disposition (HTTP Header Field)

Content-Disposition takes one of two values, `inline' and `attachment'.  `Inline' indicates that the entity should be immediately displayed to the user, whereas `attachment' means that the user should take additional action to view the entity (i.e., to open or save). - http://www.ietf.org/rfc/rfc2183.txt

Saturday, August 4, 2018

Mosaic

People are more like mosaic tiles than pieces of a puzzle. Puzzle pieces fit just right and make a clear picture. Mosaic tiles are broken and have rough edges. The picture they construct is best seen from a higher perspective. But there is a beauty and flexibility and creativity made possible by the ragged forms.

Mosaic was also one of the early web browsers. http://www.ncsa.illinois.edu/enabling/mosaic

Thursday, September 5, 2013

polyfill

What is a polyfill?

A polyfill is essentially code that would allow you to have some specific functionality that you expect in current or “modern” browsers to also work in other browsers that do not have the support for that functionality built in.

Why is the term polyfill used?

The term polyfill itself is meant to create an image of filling holes and cracks in a wall with some glue to allow you to paint over it. In this analogy, the browser is like the wall, and the polyfill is like the glue which allows you to treat the browser/wall just like any other browser.

Reference: http://www.programmerinterview.com/index.php/html5/html5-polyfill/