Accessible websites are crucial for those unlucky enough to have some form of disability or limited sight, hearing or movement. Unfortunately it is extremely "easy" to accidentally preventing websites from working with accessibility tools. It is our responsibility as developers to make sure the systems we develop can be used by anyone, and to achieve that we need the right "tools".
In this talk I not only explain how to write proper, accessible HTML, but I also show you what happens if you do not. We look at how HTML5 and WAI-ARIA can improve navigation, understanding and perception, and how to make screen readers react to changes made by JavaScript code.
By watching this talk you will learn the most common pitfalls and the best techniques when it comes to accessibility.
jQuery Mobile has been integrated in APEX since version 4.2 and building a mobile web application with APEX seems magically easy ever since. Once you start a mobile project you will be confronted with a number of challenges related to the jQuery Mobile frameworks mechanisms. This session tends to explain the fundamentals that are important to know for APEX developers and how to deal with these in APEX development.
When creating a mobile web application with APEX, knowledge of how jQuery Mobile works and how it is different from what we are used to as APEX developers is essential, I learned this during projects. This session will explain the important jQuery Mobile framework mechanisms and how to deal with these in APEX: Page loading and submitting data; customizing the user interface elements; debugging, testing and inspecting on actual mobile devices.
This document provides an overview of designing for the web, covering topics such as HTML page structure, basic HTML components, the difference between content and style, CSS selectors, the CSS box model, responsive design, and more. It begins with introductions to the presenter and presentation content. Examples and explanations are provided throughout to illustrate key concepts in web design.
Get the Look and Feel You Want in Oracle APEXJorge Rimblas
You just received an image or layered file from marketing with the design for an application you need to build. You're wondering what to do. How do I translate this into a usable APEX template? APEX provides great flexibility that allows your applications to fit within your corporate visual theme, but many people don't realize that the APEX built-in themes are not static or your only option. HTML and CSS can be daunting when your expertise lies within the database realm. This session will show you that a little understanding goes a long way.
This document discusses WordPress themes and child themes. It begins by defining what a theme is and what themes do. It then explains what components make up a theme. The document recommends choosing a theme based on UI/UX rather than functionality so that functionality can be added and retained through plugins. It defines what a child theme is and how it allows customizing a parent theme while keeping customizations separate. The document provides instructions for manually creating a child theme and using a plugin. It discusses best practices for working with child themes such as overriding parent templates.
Lose Your Head! Re-imagining WordPress's Role in Content PresentationJeremy Ward
Since the introduction of the REST API, developers have been seeking ways to leverage the benefits of WordPress for content creation, while offering new options for presenting that information on the client side. Native mobile apps, JavaScript front-ends, static sites – the possibilities are endless.
Let’s take a closer look at the benefits and limitations of going “headless” with WordPress, find out what the hype is about, and determine whether this approach is something that could benefit you or your clients.
The document provides information on adding images and links to HTML documents. Some key points include:
- The <a> tag is used to define links, with the "href" attribute specifying the link destination. Links can be absolute, relative, or email links.
- The <img> tag inserts images, requiring the "src" attribute to specify the image file path. Images can also have an "alt" attribute to provide alternative text.
- Accessible links use descriptive text, avoid generic text like "click here", and don't open links in new windows without indication.
- Images improve user experience and engagement. They are added using the <img> tag and can also be made into
jQuery Mobile has been integrated in APEX since version 4.2 and building a mobile web application with APEX seems magically easy ever since. Once you start a mobile project you will be confronted with a number of challenges related to the jQuery Mobile frameworks mechanisms. This session tends to explain the fundamentals that are important to know for APEX developers and how to deal with these in APEX development.
When creating a mobile web application with APEX, knowledge of how jQuery Mobile works and how it is different from what we are used to as APEX developers is essential, I learned this during projects. This session will explain the important jQuery Mobile framework mechanisms and how to deal with these in APEX: Page loading and submitting data; customizing the user interface elements; debugging, testing and inspecting on actual mobile devices.
This document provides an overview of designing for the web, covering topics such as HTML page structure, basic HTML components, the difference between content and style, CSS selectors, the CSS box model, responsive design, and more. It begins with introductions to the presenter and presentation content. Examples and explanations are provided throughout to illustrate key concepts in web design.
Get the Look and Feel You Want in Oracle APEXJorge Rimblas
You just received an image or layered file from marketing with the design for an application you need to build. You're wondering what to do. How do I translate this into a usable APEX template? APEX provides great flexibility that allows your applications to fit within your corporate visual theme, but many people don't realize that the APEX built-in themes are not static or your only option. HTML and CSS can be daunting when your expertise lies within the database realm. This session will show you that a little understanding goes a long way.
This document discusses WordPress themes and child themes. It begins by defining what a theme is and what themes do. It then explains what components make up a theme. The document recommends choosing a theme based on UI/UX rather than functionality so that functionality can be added and retained through plugins. It defines what a child theme is and how it allows customizing a parent theme while keeping customizations separate. The document provides instructions for manually creating a child theme and using a plugin. It discusses best practices for working with child themes such as overriding parent templates.
Lose Your Head! Re-imagining WordPress's Role in Content PresentationJeremy Ward
Since the introduction of the REST API, developers have been seeking ways to leverage the benefits of WordPress for content creation, while offering new options for presenting that information on the client side. Native mobile apps, JavaScript front-ends, static sites – the possibilities are endless.
Let’s take a closer look at the benefits and limitations of going “headless” with WordPress, find out what the hype is about, and determine whether this approach is something that could benefit you or your clients.
The document provides information on adding images and links to HTML documents. Some key points include:
- The <a> tag is used to define links, with the "href" attribute specifying the link destination. Links can be absolute, relative, or email links.
- The <img> tag inserts images, requiring the "src" attribute to specify the image file path. Images can also have an "alt" attribute to provide alternative text.
- Accessible links use descriptive text, avoid generic text like "click here", and don't open links in new windows without indication.
- Images improve user experience and engagement. They are added using the <img> tag and can also be made into
The WAI-ARIA specification has been a shot in the arm for accessibility on the web. In this talk, I'll cover the basics of building accessible web applications without ARIA, and then how to add ARIA for some extra accessibility magic.
If you’re building Oracle APEX applications, there’s a good chance that they are business-centric applications that will mostly be used by employees of your organization. The main goal of the user interface of these applications is to be functional and intuitive, not flashy and eccentric. Throw in the challenges of cross-browser compatibility and mobile support, and designing a user interface gets pretty complex. This session will outline some techniques and tools that can be applied when designing user interfaces for these business-centric applications. All solutions will be presented in a format that does not require advanced graphics design experience.
Thinkful - Frontend Crash Course - Intro to HTML/CSSTJ Stalcup
This document provides an overview of an introductory HTML/CSS crash course. It introduces the instructor and Thinkful, discusses the goals of learning core HTML and CSS concepts through building a basic website. It covers key topics like how the web works, HTML tags and elements, CSS selectors, properties and values, and linking a CSS stylesheet to HTML. The document emphasizes practicing the concepts through building assignments and challenges students to keep learning outside of the course.
Oracle Application Express is using its own syntax to pass URL parameters, called the f?p syntax. In fact, there is only one standard URL search-path parameter: "p". This makes APEX URL’s less readable for users and very difficult to understand for search engines. In my session I will explain and demonstrate a few techniques to use standard URL syntax in conjunction with APEX, in order to present pretty URL’s to users and search engines, just using the APEX Listener and the database.
Code & design your first website (3:16)Thinkful
This document provides an overview of how to code and design a first website. It discusses HTML, CSS, and web development fundamentals. It guides the reader through building a simple "About Me" webpage using Codepen.io to practice HTML and CSS. Tips are provided on downloading the code to a text editor and making the page viewable locally. The document also briefly touches on additional layout concepts like inline vs block elements and the box model. Overall, the document serves as an introductory tutorial for someone with little to no experience to code their first website.
Mit Oracle Application Express entwickelt man im Browser Applikationen, die im Browser laufen. Damit ist der Browser eines der wichtigsten Werkzeuge eines APEX Entwicklers. Beim Entwickeln mit SQL oder PL/SQL nutzen wir die reiche Funktionalitäten von IDEs (SQL Developer, TOAD, PLSQL Developer, ...) um produktive zu arbeiten. Das bauen von Webapplikationen beschränkt sich aber nicht die Datenbank. Man wird auch mit Techniken wie HTML, CSS und JavaScript konfrontiert.
Obwohl APEX die Komplexität, die diese Techniken mit sich mitbringen, zu einem großen Teil mit dem deklarativen Aufbau des Frameworks verbergen kann, desto mehr man mit APEX entwickelt, desto mehr wird man gezwungen sich mit der darunterliegenden Technik zu befassen. Das ist der Moment, dass man als Entwickler den Browser nicht allein als Applikations-Fenster, sondern auch als modernes Entwickeltool einsetzt.
Debugging, Testen, Performance Tuning, dies sind nur rein paar Möglichkeiten die durch den Browser unterstützt werden. In meiner Präsentation werde ich die wichtigsten Funktionen und Features moderner Browser, die für uns APEX Entwickler das Leben einfacher machen, erläutern und demonstrieren.
Abstract #236765 advanced essbase java api tips and trickstimtow
This document provides tips and tricks for using the Advanced Essbase Java API. It discusses getting started with a good IDE and required libraries. It also covers understanding the object model and task sequences, connecting to Essbase databases in embedded and 3-tier modes, accessing member information through IEssMember objects and member strings, using the fast grid API to retrieve data, and best practices for building software like using source code control, automating build scripts, and implementing robust logging.
This document provides an introduction to HTML and CSS for building websites. It begins with introductions and background on the instructor and Thinkful. It then discusses why students may be interested in learning web development. The document proceeds to cover basic HTML tags and elements to build a simple website, then introduces CSS to style the HTML. Key concepts of CSS like selectors, properties, and values are explained. Students are given challenges to practice these new skills. Finally, tips are provided for continuing to learn and information on Thinkful's programs is shared.
The document discusses using jQuery Mobile to create mobile web applications in Oracle Application Express, including why to use jQuery Mobile, its basic page structure and components, customizing styles and forms, and how jQuery Mobile is supported in newer versions of Application Express. It also provides code examples and demonstrations of creating mobile-friendly lists, buttons, and other elements in Application Express using jQuery Mobile.
The document provides an overview of designing Drupal themes. It discusses common tools used to design themes such as Photoshop, Fireworks, and Illustrator. It also discusses Drupal-specific tools like Firebug and the Theme Developer module. The presentation covers designing for Drupal concepts like regions, blocks, and views. It provides examples of existing Drupal themes and recommendations for naming conventions, image preparation, CSS organization, and common theme techniques like CSS resets and menu placement.
In this presentation Lou Crocker, Senior Sales Engineer at Sencha and John Ferguson, Sr. Field Engineer at Pivotal, build a Twitter search app using Sencha and Spring frameworks.
This document provides guidance on keeping website content accessible. It discusses writing accessible web copy by focusing on readability, using short paragraphs and clear headings. Images should include descriptive alt text and consider colorblindness. Videos and podcasts require captions, transcripts and audio descriptions. Tables require proper HTML markup. The presenter encourages testing with tools like WAVE and considering the needs of people with disabilities when creating and editing content.
This document appears to be a presentation about reusable components for Adobe developers. It discusses different models for reusable components, including direct reuse, direct reuse with context, and extensible components. It provides examples like foundation image and list components. It also covers best practices and anti-patterns to consider when developing reusable components. The presentation was given at a CIRCUIT event hosted by CITYTECH for Adobe developers.
Golden Rules for Effective Alt-Text. AbilityNet Webinar, March 2014AbilityNet
This month's webinar is all about alt-text and labels and will help anyone who produces content for the web, whatever their technical skills.
You could be a developer, a site editor or anyone who puts content on any website. Just follow our golden rules to make your content more accessible to your visitors, more visible to search engines and more compliant to technical and legal standards
This 20-minute presentation provides an introduction to several HTML5 semantic tags: article, section, aside, header, footer, nav. Includes how you can address browser compatibility issues.
ARIA is a W3C specification that can be used to dramatically improve the accessibility of custom widgets, especially for users of screen readers. This talk provides practical tips and design patterns for using ARIA to create accessible user interfaces that work across all of the various combinations of browsers and screen readers that support ARIA. Additionally, this talk will focus on the tools and methodologies developers need to test ARIA in order to ensure the best possible user experience.
- Flickr uses PHP for its page and application logic, along with technologies like Smarty, PEAR, Perl, and Java. The site has over 60,000 lines of PHP code and templates.
- The logical architecture includes page logic, application logic, photo storage, APIs, templates, third-party apps. The physical architecture includes static servers, database servers, and node servers.
- PHP is used for page and application logic. Smarty is used for templating. MySQL is used for storage. Java is used in the node service. Flickr scales horizontally by adding more hardware over time.
Single Page Application Development with backbone.js and Simple.WebChris Canal
This document summarizes a presentation about developing single page applications using Backbone.js and Simple.Web. It discusses Backbone.js and its core components like models, views and routers. It also covers libraries that are commonly used with Backbone like Underscore, Handlebars and RequireJS. Finally, it provides an overview of Simple.Web, a SOLID-based REST framework that can be used with Backbone.js applications.
This document provides best practices and guidelines for writing HTML code, including:
- The importance of front-end code on user experience.
- General guidelines like applying consistency and designing before implementing.
- Details on HTML document anatomy like specifying DOCTYPE and including metadata tags.
- Tips for semantic authoring, common elements, attributes, and accessibility/usability features.
- Common mistakes to avoid like forgetting to close tags, incorrect DOCTYPE, improperly nesting tags, and more.
The WAI-ARIA specification has been a shot in the arm for accessibility on the web. In this talk, I'll cover the basics of building accessible web applications without ARIA, and then how to add ARIA for some extra accessibility magic.
If you’re building Oracle APEX applications, there’s a good chance that they are business-centric applications that will mostly be used by employees of your organization. The main goal of the user interface of these applications is to be functional and intuitive, not flashy and eccentric. Throw in the challenges of cross-browser compatibility and mobile support, and designing a user interface gets pretty complex. This session will outline some techniques and tools that can be applied when designing user interfaces for these business-centric applications. All solutions will be presented in a format that does not require advanced graphics design experience.
Thinkful - Frontend Crash Course - Intro to HTML/CSSTJ Stalcup
This document provides an overview of an introductory HTML/CSS crash course. It introduces the instructor and Thinkful, discusses the goals of learning core HTML and CSS concepts through building a basic website. It covers key topics like how the web works, HTML tags and elements, CSS selectors, properties and values, and linking a CSS stylesheet to HTML. The document emphasizes practicing the concepts through building assignments and challenges students to keep learning outside of the course.
Oracle Application Express is using its own syntax to pass URL parameters, called the f?p syntax. In fact, there is only one standard URL search-path parameter: "p". This makes APEX URL’s less readable for users and very difficult to understand for search engines. In my session I will explain and demonstrate a few techniques to use standard URL syntax in conjunction with APEX, in order to present pretty URL’s to users and search engines, just using the APEX Listener and the database.
Code & design your first website (3:16)Thinkful
This document provides an overview of how to code and design a first website. It discusses HTML, CSS, and web development fundamentals. It guides the reader through building a simple "About Me" webpage using Codepen.io to practice HTML and CSS. Tips are provided on downloading the code to a text editor and making the page viewable locally. The document also briefly touches on additional layout concepts like inline vs block elements and the box model. Overall, the document serves as an introductory tutorial for someone with little to no experience to code their first website.
Mit Oracle Application Express entwickelt man im Browser Applikationen, die im Browser laufen. Damit ist der Browser eines der wichtigsten Werkzeuge eines APEX Entwicklers. Beim Entwickeln mit SQL oder PL/SQL nutzen wir die reiche Funktionalitäten von IDEs (SQL Developer, TOAD, PLSQL Developer, ...) um produktive zu arbeiten. Das bauen von Webapplikationen beschränkt sich aber nicht die Datenbank. Man wird auch mit Techniken wie HTML, CSS und JavaScript konfrontiert.
Obwohl APEX die Komplexität, die diese Techniken mit sich mitbringen, zu einem großen Teil mit dem deklarativen Aufbau des Frameworks verbergen kann, desto mehr man mit APEX entwickelt, desto mehr wird man gezwungen sich mit der darunterliegenden Technik zu befassen. Das ist der Moment, dass man als Entwickler den Browser nicht allein als Applikations-Fenster, sondern auch als modernes Entwickeltool einsetzt.
Debugging, Testen, Performance Tuning, dies sind nur rein paar Möglichkeiten die durch den Browser unterstützt werden. In meiner Präsentation werde ich die wichtigsten Funktionen und Features moderner Browser, die für uns APEX Entwickler das Leben einfacher machen, erläutern und demonstrieren.
Abstract #236765 advanced essbase java api tips and trickstimtow
This document provides tips and tricks for using the Advanced Essbase Java API. It discusses getting started with a good IDE and required libraries. It also covers understanding the object model and task sequences, connecting to Essbase databases in embedded and 3-tier modes, accessing member information through IEssMember objects and member strings, using the fast grid API to retrieve data, and best practices for building software like using source code control, automating build scripts, and implementing robust logging.
This document provides an introduction to HTML and CSS for building websites. It begins with introductions and background on the instructor and Thinkful. It then discusses why students may be interested in learning web development. The document proceeds to cover basic HTML tags and elements to build a simple website, then introduces CSS to style the HTML. Key concepts of CSS like selectors, properties, and values are explained. Students are given challenges to practice these new skills. Finally, tips are provided for continuing to learn and information on Thinkful's programs is shared.
The document discusses using jQuery Mobile to create mobile web applications in Oracle Application Express, including why to use jQuery Mobile, its basic page structure and components, customizing styles and forms, and how jQuery Mobile is supported in newer versions of Application Express. It also provides code examples and demonstrations of creating mobile-friendly lists, buttons, and other elements in Application Express using jQuery Mobile.
The document provides an overview of designing Drupal themes. It discusses common tools used to design themes such as Photoshop, Fireworks, and Illustrator. It also discusses Drupal-specific tools like Firebug and the Theme Developer module. The presentation covers designing for Drupal concepts like regions, blocks, and views. It provides examples of existing Drupal themes and recommendations for naming conventions, image preparation, CSS organization, and common theme techniques like CSS resets and menu placement.
In this presentation Lou Crocker, Senior Sales Engineer at Sencha and John Ferguson, Sr. Field Engineer at Pivotal, build a Twitter search app using Sencha and Spring frameworks.
This document provides guidance on keeping website content accessible. It discusses writing accessible web copy by focusing on readability, using short paragraphs and clear headings. Images should include descriptive alt text and consider colorblindness. Videos and podcasts require captions, transcripts and audio descriptions. Tables require proper HTML markup. The presenter encourages testing with tools like WAVE and considering the needs of people with disabilities when creating and editing content.
This document appears to be a presentation about reusable components for Adobe developers. It discusses different models for reusable components, including direct reuse, direct reuse with context, and extensible components. It provides examples like foundation image and list components. It also covers best practices and anti-patterns to consider when developing reusable components. The presentation was given at a CIRCUIT event hosted by CITYTECH for Adobe developers.
Golden Rules for Effective Alt-Text. AbilityNet Webinar, March 2014AbilityNet
This month's webinar is all about alt-text and labels and will help anyone who produces content for the web, whatever their technical skills.
You could be a developer, a site editor or anyone who puts content on any website. Just follow our golden rules to make your content more accessible to your visitors, more visible to search engines and more compliant to technical and legal standards
This 20-minute presentation provides an introduction to several HTML5 semantic tags: article, section, aside, header, footer, nav. Includes how you can address browser compatibility issues.
ARIA is a W3C specification that can be used to dramatically improve the accessibility of custom widgets, especially for users of screen readers. This talk provides practical tips and design patterns for using ARIA to create accessible user interfaces that work across all of the various combinations of browsers and screen readers that support ARIA. Additionally, this talk will focus on the tools and methodologies developers need to test ARIA in order to ensure the best possible user experience.
- Flickr uses PHP for its page and application logic, along with technologies like Smarty, PEAR, Perl, and Java. The site has over 60,000 lines of PHP code and templates.
- The logical architecture includes page logic, application logic, photo storage, APIs, templates, third-party apps. The physical architecture includes static servers, database servers, and node servers.
- PHP is used for page and application logic. Smarty is used for templating. MySQL is used for storage. Java is used in the node service. Flickr scales horizontally by adding more hardware over time.
Single Page Application Development with backbone.js and Simple.WebChris Canal
This document summarizes a presentation about developing single page applications using Backbone.js and Simple.Web. It discusses Backbone.js and its core components like models, views and routers. It also covers libraries that are commonly used with Backbone like Underscore, Handlebars and RequireJS. Finally, it provides an overview of Simple.Web, a SOLID-based REST framework that can be used with Backbone.js applications.
This document provides best practices and guidelines for writing HTML code, including:
- The importance of front-end code on user experience.
- General guidelines like applying consistency and designing before implementing.
- Details on HTML document anatomy like specifying DOCTYPE and including metadata tags.
- Tips for semantic authoring, common elements, attributes, and accessibility/usability features.
- Common mistakes to avoid like forgetting to close tags, incorrect DOCTYPE, improperly nesting tags, and more.
In this session we'll review the checks you must go through before deciding whether to use an ARIA role or attribute, reveal our favorites, discuss the ones that need more user agent support, and show you how you can help us make it happen.
You know it's important for your web project to be accessible to people who use all kinds of assistive technology to access the internet. But all the guidelines for web accessibility you can find don't go much beyond "make sure all your images have alt text", and all the resources you can find treat "accessibility" as a synonym for "making your site work in a screen reader". You know there are other things you should be doing and other forms of assistive technology you should be accomodating, but all the best practices documents are a complicated morass of contradicting information (if you can find best practices documents at all.)
Have no fear! This tutorial gives you a number of concrete steps to take to make things more accessible.
This presentation has downloadable notes and exercises available at http://denise.dreamwidth.org/tag/a11y . Video of the talk should be available later.
Ember.js brings some new and interesting conventions to the table for designing single page applications. In this talk, I'll be covering the key pieces of Ember, how it compares to other frameworks, and the backstory of why it was created.
Accessibility Hacks Wordcamp Manchester October 2018Graham Armfield
A bunch of small accessibility tweaks that WordPress theme builders can make to improve the accessibility of their products.
Contains a section on making SVG files accessible to screen reader users. And then some CSS techniques that can help trap accessibility gotchas when building themes, and for content authors when they preview posts or pages.
Revised version of my presentation - first delivered to WordCamp Manchester in 2019.
Presentation looks at some small tweaks to HTML and CSS that can make your site a little more accessible.
Covers: SVG images, screen reader text, some CSS to help when building your web templates/themes, and some CSS that can help show your content authors where they may have made some accessibility mistakes.
The document discusses using SVG images and CSS techniques to improve accessibility in WordPress themes. It provides tips for using SVG images in an accessible way, such as adding the "role=img" attribute to SVG files and using the <title> or <desc> elements for inline SVGs. It also suggests using CSS classes to hide non-essential text from sighted users while retaining it for screen readers. The document demonstrates how highlighting different page elements in the CSS can help test that landmarks and other accessibility standards are properly implemented.
SVG is often used for content, linked icons, and buttons. Learn which coding methods perform best across a variety of screen reader and browser combinations. By @DennisL
Web Accessibility Top 10 - LCC (1/2 day workshop, August 2013)Carrie Anton
A half day workshop walks people through common accessibility issues on the web, including good reasons why to accessible. Great for web designers, developers, teachers and IT trainers.
This document provides an overview of accessibility best practices for semantic HTML, headings, lists, emphasis elements, keyboard navigation, tabindex, component states, consistency, context, abbreviations, alt text, font size and color contrast, zoom, and testing. Key recommendations include using semantic HTML for structure and meaning, logical heading and list hierarchies, emphasis elements semantically, logical tab order, providing context for components, meaningful alt text for images, font sizes above 11px, sufficient color contrast, support for zooming, and testing with assistive technologies.
End to-End SPA Development Using ASP.NET and AngularJSGil Fink
This document discusses end-to-end single page application development using ASP.NET and AngularJS. It begins with an introduction to SPAs and their benefits. It then covers key SPA building blocks like HTML5, JavaScript libraries, Ajax, REST, routing, and AngularJS components like controllers, services, directives and routing. It demonstrates using ASP.NET MVC and Web API for the backend API and services. AngularJS is used for the frontend framework. The presentation includes demos of key concepts and a full example app to demonstrate an end-to-end SPA. It concludes with questions and resources for further learning.
The document discusses best practices for organizing and structuring CSS code, including:
1. Using inheritance, cascading, and specificity principles to determine which styles take precedence.
2. Avoiding inline styles, <br> tags for spacing, for empty elements, and tables for layout as they harm semantics and structure.
3. Preferring class names over IDs due to lower specificity, and using flexbox, grid, rem/em units, and preprocessing with LESS/Sass for modularity and responsive design.
The document discusses best practices for effective SEO implementation in Adobe WEM. It covers optimizing page titles, descriptions and navigation; emphasizing proper content structure using semantic HTML; incorporating assets from DAM by optimizing filenames and metadata like ALT text; using microformats like Google rich snippets and social metadata; and empowering content authors through custom tools. The agenda outlines optimization techniques and leveraging out-of-the-box functionality while avoiding link building or social media integration.
This document provides an overview of layout managers and skins in Oracle ADF Faces. It discusses:
1) The benefits of using layout managers such as abstraction from HTML, consistent layout behavior across browsers, and managing browser geometry. It describes stretchable vs flowing layouts.
2) Tips for working with layout managers such as starting with a stretchable outer frame and placing flowing islands inside.
3) An introduction to skins including how they work, the artifacts that make up a skin, and how skinning differs from regular CSS. It provides examples of using different selectors to style parts of a component.
Making Websites Accessible to People with DisabilitiesChristian Brink
It’s important to make sure that your website is accessible by everyone, regardless of disability. Learn how to improve the accessibility of your website.
The document provides an overview of WCAG 2.0 guidelines for web accessibility. It discusses the four principles of WCAG 2.0 - Perceivable, Operable, Understandable, and Robust. For each principle, it lists the guidelines and requirements for level A and AA conformance. It also provides an overview of WAI-ARIA, which contains additional accessibility attributes for developers. The document includes resources for web accessibility extensions, applications, and general information.
Ähnlich wie Resistance is futile: Start writing accessible websites now! (20)
This document provides an overview of accessibility best practices for developers and designers. It discusses key topics like headings, landmarks, and disclosure widgets to help structure content in an accessible way. It also covers testing strategies like using a keyboard, zooming, browser extensions, screen readers and user testing to evaluate accessibility. The overall message is that accessibility needs to be considered in design and development, and thoroughly tested, to ensure usability for all people.
The document summarizes the new requirements in WCAG 2.1 for accessible web design. It lists the 17 new success criteria added in WCAG 2.1 and provides examples and explanations for some of these new criteria, including requirements for identifying common purposes of user interface elements, ensuring reflow of content at different zoom levels, specifying text spacing, and allowing concurrent input mechanisms. It also indicates some success criteria from previous versions that were removed or combined in WCAG 2.1.
Booster 2017 - from accessibility n00b to pro in 1.5 hrsVegard Haugstvedt
You have (probably?) heard about accessibility ("universell utforming" in Norwegian), but do you know what it is? How to use it and how to design, develop and test for it? No? Then this is the workshop for you! And even if you are experienced and know what a11y stands for, you might pick up a trick or two.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Top 9 Trends in Cybersecurity for 2024.pptxdevvsandy
Security and risk management (SRM) leaders face disruptions on technological, organizational, and human fronts. Preparation and pragmatic execution are key for dealing with these disruptions and providing the right cybersecurity program.
WWDC 2024 Keynote Review: For CocoaCoders AustinPatrick Weigel
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
E-commerce Development Services- Hornet DynamicsHornet Dynamics
For any business hoping to succeed in the digital age, having a strong online presence is crucial. We offer Ecommerce Development Services that are customized according to your business requirements and client preferences, enabling you to create a dynamic, safe, and user-friendly online store.
UI5con 2024 - Boost Your Development Experience with UI5 Tooling ExtensionsPeter Muessig
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
UI5con 2024 - Bring Your Own Design SystemPeter Muessig
How do you combine the OpenUI5/SAPUI5 programming model with a design system that makes its controls available as Web Components? Since OpenUI5/SAPUI5 1.120, the framework supports the integration of any Web Components. This makes it possible, for example, to natively embed own Web Components of your design system which are created with Stencil. The integration embeds the Web Components in a way that they can be used naturally in XMLViews, like with standard UI5 controls, and can be bound with data binding. Learn how you can also make use of the Web Components base class in OpenUI5/SAPUI5 to also integrate your Web Components and get inspired by the solution to generate a custom UI5 library providing the Web Components control wrappers for the native ones.
6. ACCESSIBILITY
API
Accessible name
• Label, combined text children, alt
attributes, etc.
Value and properties
• The value of a form element is
handled by the browser.
• Other properties include min and max
values, etc.
State
• Normally set by the browser, but will
need to be handled by custom
components.
Role
• Handled by native HTML element, but
can be overriden with «role» attribute.
7. Bad example Good example
ACCESSIBILITY API – ACCESSIBLE NAME
Examples from https://www.smashingmagazine.com/2015/03/web-accessibility-with-accessibility-api/
17. LINKS VS
BUTTONS
• Links Navigation
• Buttons Action
• Do not create custom
buttons or links unless
you know what you are
doing!
18. LINKS AND
BUTTONS
– TIPS
• Never remove underline for
links!
• Default tabindex=‘’0’’
• Images in link - Does it have a
purpose? Add alt-text.
• Links and buttons should react
to mouse click, enter and space
20. IMAGES
With text in image
• If the image contains text
that is meaningful and not
otherwise present
Use alt-attribute
• If the text is only for visual
effects or the text is present
elsewhere on the site
Use empty alt-attribute
21. IMAGES
Image in link or button
• If it would be difficult to
understand what the link
or buttons does without
the image there
Use alt-attribute
22. IMAGES
Image gives meaning to the
page or context
• If it is a simple graphic or
photograph
Use alt-attribute
• If it is a graph or complex piece
of information
Use alt-attribute
• If it shows content that is
redundant to text nearby
Use empty alt-attribute
24. IMAGES
Tips for choosing alt-texts
• Image you are reading a
website aloud over the phone.
• Put the most important
information first
• The text should be as concise
as possible.
• Do not start with «image of»,
«icon», etc.
• Logos are exempt from the
rules
25. SVG-
IMAGES
Referenced with src-attribute
• Use the methods described for
images in general
Inline SVG
• Provide a title within the svg-tag
• Reference the title with aria-
labelled-by on the svg-tag.
29. FORMS -
LABELS
• Associate label with input
element.
• Visually hide the label or
use aria-labelledby if
purpose is clear.
30. FORMS –
INSTRUCTIONS
• Within labels
• Outside of label
• aria-labelledby
• aria-describedby
• Beware of relying on
placeholders!
• Remember to mark required
items both programmatically
and visually!
31. FORMS –
GROUPING
CONTROLS
• Fieldset
• Legend
• For radio buttons,
checkboxes or related fields
• Role=«group»
• Use aria-labelledby to
provide label for the group
32. FORMS –
FEEDBACK
• Provide feedback next to
the input with an error
• Alert users with assistive
technology (aria-live)
• Don’t lose data
36. “A big part of accessibility is […] an
easily met responsibility of web
developers:
Know your job, use your tools well, and
many pieces will fall into place as if by
magic.”
- Léonie Watson & Chaals McCathie Nevile
Hinweis der Redaktion
[45:00]
– Who am I? (Lead consultant at Itera, husband, father, paternity leave)
– Brief summary of topic? A practical introduction to creating accessible websites.
– Why am I interested in a11y? Color blind, interested in user-centered design, likes to work at the front of frontend. Worked on Storebrand.ny
[44:00]
[43:30]
[43:00]
Perceivable – Providing text alternatives, presenting content so it can be perceived (color contrasts), controls for time-based media
Operable – Keyboard accessible, help users understand where on the page they are, don’t let users time out and finally preventing seizures.
Understandable – Make text readable, give assitance to prevent user errors and make the website be predictable in both presentation and operation.
Robust – Make the webpage work with any user agent, like browsers, plugins, «article» readers, etc.
[41:00]
So, how does the assistive technologies know what to present to the user?
The image on the right shows an example of an Accessibility Tree, which is a modified DOM tree.
This removes everything that is only relevant for visual presentation.
https://creativecommons.org/licenses/by/3.0/
[40:00]
[38:30]
[37:00]
[35:30]
[35:00] Let’s start by looking at the bigger picture: The HTML document, regions and content structure.
[34:30]
[33:30] Page regions enable assistive technology to indentify regions of the document, sometimes enabling users to jump to that content, or notifying the user of its precence.
The header element is used for the region at the top of the page with logo, search, navigation, etc. It can also be used inside articles or sections, and in that case is associated only with that region.
Similarly, the footer element is used for the area at the bottom of the page, where you typically can find copyright information, privacy statements and disclaimers. The footer element can also be used inside articles and sections.
The nav element is used for navigation menus. Several of these can be used on the same page, but they should be named to make it clear what navigation menu they contain. Screen readers typically has shortcuts to jump to the menu, so marking it as such is essential to speed up navigation.
https://www.w3.org/WAI/tutorials/page-structure/
The main content should also be marked up using the main tag. This is both useful for screen readers that has shortcuts for jumping to the main content, but also for other user agents, like article readers/rss feeds that only show the relevant parts of a page, or read-mode in browsers like Edge, where only the main content is shown.
Complementary or related content, which support the main content, but can exist on its own, should be marked up using the aside tag.
In addition, you can use the article and section tags to mark up individual parts of the content.
These tags as well as the main and aside tags should ideally begin with a heading to provide an accessible name for the region, which will be read aloud to users of screen readers, making it easier to identify regions. These headings should have an ID, that the region tag references using aria-labelledby. Another option, where the label should not visibly appear at the page, use aria-label, like I have done with the navigation element in the example here.
[32:30]
The main content should also be marked up using the main tag. This is both useful for screen readers that has shortcuts for jumping to the main content, but also for other user agents, like article readers/rss feeds that only show the relevant parts of a page, or read-mode in browsers like Edge, where only the main content is shown.
Complementary or related content, which support the main content, but can exist on its own, should be marked up using the aside tag.
In addition, you can use the article and section tags to mark up individual parts of the content.
These tags as well as the main and aside tags should contain a heading to provide an accessible name for the region, which will be read aloud to users of screen readers, making it easier to identify regions. These headings should have an ID, that the region tag references using aria-labelledby. Another option, where the label should not visibly appear at the page, use aria-label, like I have done with the navigation element in the example here.
https://www.w3.org/WAI/tutorials/page-structure/
[31:00]
Essential to organize the content of a page.
Should be nested logically by rank or level. Headings on equal or higher ranks start a new section, while lower ranks start a subsection as part of the current section.
Assistive technology provides means to jump up and down in the hierarchy
[30:00]
As mentioned, HTML5 introduced several new tags for semantically organizing content, like the article and section tags.
Articles are complete or independent compositions in a web page, like items in a shopping site or a news article on a news site.
Sections are used for general regions of a page, and can be used both outside and inside of articles.
In addition to these new tags, we have the old tags, like paragraph, lists, and so on. I am amazed at how quickly someone will resort to writing lists with dashes and newline tags instead of using actual list tags.
These tags are important, because they inform assistive technology what type of content it is and how to interact with it, as well as providing default styling (which you may override as long as you follow the rules).
[28:00]
[27:30]
Links lead the user to a new page or somewhere else on the same page (navigation)
Buttons perform an action on the same page – toggle, submit form, etc.
Do not create custom buttons or links unless you know what you are doing!
[26:30]
Removing underline is almost never a good idea for normal links. Exceptions are for menu items and similar, where you indicate in another fashon that it is a link.
Do not remove the href attribute. Doing so will remove the link from the taborder. At least add tabindex if you HAVE TO skip href, but is so you are probably not using the right element anyhow.