DOCSLIB.ORG

[MS-HTML52]: Microsoft Edge HTML 5.2 Standards Support Document

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
[MS-HTML52]: Microsoft Edge HTML 5.2 Standards Support Document [MS-HTML52]: Microsoft Edge HTML 5.2 Standards Support Document Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map. Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks. Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred. Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise. Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it. Support. For questions and support, please contact [email protected]. 1 / 108 [MS-HTML52] - v20180605 Microsoft Edge HTML 5.2 Standards Support Document Copyright © 2018 Microsoft Corporation Release: June 5, 2018 Revision Summary Date Revision History Revision Class Comments 6/5/2018 1.0 New Released new document. 2 / 108 [MS-HTML52] - v20180605 Microsoft Edge HTML 5.2 Standards Support Document Copyright © 2018 Microsoft Corporation Release: June 5, 2018 Table of Contents 1 Introduction ............................................................................................................ 7 1.1 Glossary ........................................................................................................... 7 1.2 References ........................................................................................................ 7 1.2.1 Normative References ................................................................................... 7 1.2.2 Informative References ................................................................................. 7 1.3 Microsoft Implementations .................................................................................. 7 1.4 Standards Support Requirements ......................................................................... 8 1.5 Notation ............................................................................................................ 8 2 Standards Support Statements ................................................................................ 9 2.1 Normative Variations .......................................................................................... 9 2.1.1 [W3C-HTML52] Section 2.4.1. Common parser idioms ....................................... 9 2.1.2 [W3C-HTML52] Section 2.4.4.3. Floating-point numbers .................................... 9 2.1.3 [W3C-HTML52] Section 2.7.2.2. The HTMLFormControlsCollection interface ....... 10 2.1.4 [W3C-HTML52] Section 2.9.3. StructuredSerializeInternal ( value, forStorage [ , memory ] ) ................................................................................................ 10 2.1.5 [W3C-HTML52] Section 2.9.6. StructuredDeserialize ( serialized, targetRealm [ , memory ] ) ................................................................................................ 11 2.1.6 [W3C-HTML52] Section 2.9.7. StructuredSerializeWithTransfer ( value, transferList ) ............................................................................................................... 11 2.1.7 [W3C-HTML52] Section 2.9.8. StructuredDeserializeWithTransfer ( serializeWithTransferResult, targetRealm ) ..................................................... 11 2.1.8 [W3C-HTML52] Section 3.1.1. The Document object ....................................... 12 2.1.9 [W3C-HTML52] Section 3.2.2. Elements in the DOM ....................................... 12 2.1.10 [W3C-HTML52] Section 3.2.5.3. The translate attribute ................................... 13 2.1.11 [W3C-HTML52] Section 3.2.5.5. The dir attribute ........................................... 13 2.1.12 [W3C-HTML52] Section 3.2.5.7. Embedding custom non-visible data with the data- * attributes ................................................................................................ 14 2.1.13 [W3C-HTML52] Section 3.2.6. The innerText IDL attribute ............................... 15 2.1.14 [W3C-HTML52] Section 4.2.2. The title element ............................................. 15 2.1.15 [W3C-HTML52] Section 4.2.4. The link element .............................................. 16 2.1.16 [W3C-HTML52] Section 4.2.6. The style element ............................................ 16 2.1.17 [W3C-HTML52] Section 4.3.1. The body element ............................................ 17 2.1.18 [W3C-HTML52] Section 4.3.9.1. Creating an outline........................................ 17 2.1.19 [W3C-HTML52] Section 4.4.6. The ol element ................................................ 17 2.1.20 [W3C-HTML52] Section 4.5.1. The a element ................................................. 18 2.1.21 [W3C-HTML52] Section 4.5.13. The rtc element ............................................. 18 2.1.22 [W3C-HTML52] Section 4.5.26. The bdi element ............................................. 19 2.1.23 [W3C-HTML52] Section 4.7.5. The img element ............................................. 19 2.1.24 [W3C-HTML52] Section 4.7.7. The embed element ......................................... 19 2.1.25 [W3C-HTML52] Section 4.7.8. The object element .......................................... 20 2.1.26 [W3C-HTML52] Section 4.7.13. Media elements ............................................. 20 2.1.27 [W3C-HTML52] Section 4.7.13.2. Location of the media resource ..................... 21 2.1.28 [W3C-HTML52] Section 4.7.13.5. Loading the media resource .......................... 21 2.1.29 [W3C-HTML52] Section 4.7.13.6. Offsets into the media resource .................... 22 2.1.30 [W3C-HTML52] Section 4.7.13.9. Seeking ..................................................... 23 2.1.31 [W3C-HTML52] Section 4.7.14. The map element ........................................... 23 2.1.32 [W3C-HTML52] Section 4.7.15. The area element ........................................... 23 2.1.33 [W3C-HTML52] Section 4.7.16.2. Processing model ........................................ 25 2.1.34 [W3C-HTML52] Section 4.7.17. MathML ........................................................ 26 2.1.35 [W3C-HTML52] Section 4.9.5. The tbody element ........................................... 26 2.1.36 [W3C-HTML52] Section 4.9.8. The tr element ................................................ 27 2.1.37 [W3C-HTML52] Section 4.9.10. The th element .............................................. 27 2.1.38 [W3C-HTML52] Section 4.10.5. The input element .......................................... 27 2.1.39 [W3C-HTML52] Section 4.10.5.1.1. Hidden state (type=hidden) ....................... 29 3 / 108 [MS-HTML52] - v20180605 Microsoft Edge HTML 5.2 Standards Support Document Copyright © 2018 Microsoft Corporation Release: June 5, 2018 2.1.40 [W3C-HTML52] Section 4.10.5.1.4.
Load more

Recommended publications
  • Towards a Verified Range Analysis for Javascript Jits
    Towards a Verified Range Analysis for JavaScript JITs Fraser Brown John Renner Andres Nötzli Stanford, USA UC San Diego, USA Stanford, USA Sorin Lerner Hovav Shacham Deian Stefan UC San Diego, USA UT Austin, USA UC San Diego, USA Abstract Earlier this year, Google’s Threat Analysis Group identi- We present VeRA, a system for verifying the range analysis fied websites, apparently aimed at people “born in a certain pass in browser just-in-time (JIT) compilers. Browser devel- geographic region” and “part of a certain ethnic group,” that opers write range analysis routines in a subset of C++, and would install a malicious spyware implant on any iPhone verification developers write infrastructure to verify custom used to visit them. Two bugs exploited in this campaign, analysis properties. Then, VeRA automatically verifies the according to analysis by Google’s Project Zero [41, 68], were range analysis routines, which browser developers can in- in the JIT component of Safari’s JavaScript engine [5, 34]. tegrate directly into the JIT. We use VeRA to translate and The JavaScript JITs shipped in modern browsers are ma- verify Firefox range analysis routines, and it detects a new, ture, sophisticated systems developed by compilers experts. confirmed bug that has existed in the browser for six years. Yet bugs in JIT compilers have emerged in recent months as the single largest threat to Web platform security, and the CCS Concepts: • Security and privacy ! Browser se- most dangerous attack surface of Web-connected devices. curity; • Software and its engineering ! Just-in-time Unlike other compilers, browser JITs are exposed to adver- compilers; Software verification and validation; Domain sarial program input.
    [Show full text]
  • Understanding the Attack Surface and Attack Resilience of Project Spartan’S (Edge) New Edgehtml Rendering Engine
    Understanding the Attack Surface and Attack Resilience of Project Spartan’s (Edge) New EdgeHTML Rendering Engine Mark Vincent Yason IBM X-Force Advanced Research yasonm[at]ph[dot]ibm[dot]com @MarkYason [v2] © 2015 IBM Corporation Agenda . Overview . Attack Surface . Exploit Mitigations . Conclusion © 2015 IBM Corporation 2 Notes . Detailed whitepaper is available . All information is based on Microsoft Edge running on 64-bit Windows 10 build 10240 (edgehtml.dll version 11.0.10240.16384) © 2015 IBM Corporation 3 Overview © 2015 IBM Corporation Overview > EdgeHTML Rendering Engine © 2015 IBM Corporation 5 Overview > EdgeHTML Attack Surface Map & Exploit Mitigations © 2015 IBM Corporation 6 Overview > Initial Recon: MSHTML and EdgeHTML . EdgeHTML is forked from Trident (MSHTML) . Problem: Quickly identify major code changes (features/functionalities) from MSHTML to EdgeHTML . One option: Diff class names and namespaces © 2015 IBM Corporation 7 Overview > Initial Recon: Diffing MSHTML and EdgeHTML (Method) © 2015 IBM Corporation 8 Overview > Initial Recon: Diffing MSHTML and EdgeHTML (Examples) . Suggests change in image support: . Suggests new DOM object types: © 2015 IBM Corporation 9 Overview > Initial Recon: Diffing MSHTML and EdgeHTML (Examples) . Suggests ported code from another rendering engine (Blink) for Web Audio support: © 2015 IBM Corporation 10 Overview > Initial Recon: Diffing MSHTML and EdgeHTML (Notes) . Further analysis needed –Renamed class/namespace results into a new namespace plus a deleted namespace . Requires availability
    [Show full text]
  • Platform Support Matrix for SAP Business
    Platform Support Matrix PUBLIC SAP Business One Document Version: 1.28 – 2021-05-07 SAP Business One Platform Support Matrix Release 9.0 and higher Typographic Conventions Type Style Description Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Example Emphasized words or expressions. EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE Keys on the keyboard, for example, F2 or ENTER. PUBLIC © 2021 SAP SE or an SAP affiliate company. All SAP Business One Platform Support Matrix 2 rights reserved. Typographic Conventions Document History Version Date Change 1.0 2014-02-12 Release Version 1.01 2014-05-08 SAP Note 1787431 link added on XL Reporter platform support restrictions 1.02 2014-07-08 SAP Business One 9.1 added to the overview
    [Show full text]
  • Ricki-Lee - Edge of Glory (LIVE Piano Version)
    ai - edgeum - Ricki-Lee - Edge Of Glory (LIVE Piano Version) Select a Language - Microsoft Edge, now available on Android, creates one continuous browsing experience for Windows 10 users across their devices. Content and data sync seamlessly in the background, so users can browse across devices, without skipping a beat. Business Grants For Scottish Entrepreneurs | Scottish EDGE Inspired by the NAAEE mission, Microsoft Edge worked with the NAAEE to develop a web experience for innovators in environmental education and literacy to demonstrate the positive impact they have h... Microsoft Support My saves. My interests / All saves 0. Recipes Images Videos News My places. Collections + New. Help. All saves. 1/2. See all of your saved results, starting with the most recent. Next Close. All saves. Moderate. You haven't saved anything yet. From the Bing search results, select the to save a result here. Samsung Galaxy S7 and S7 edge - The Official Samsung ... The Microsoft Edge DevTools are built with TypeScript, powered by open source, optimized for modern front-end workflows, and now available as a standalone Windows 10 app in the Microsoft Store! For more on the latest features, check out DevTools in the latest update of Windows 10 (EdgeHTML 18). Test ... 2018 Ford Edge SUV | Sporty Utility for Unstoppable ... Noun. They peered over the edge of the roof. The fabric was frayed at the edge. He made us all nervous by standing so close to the edge of the cliff. She sat on the edge of the counter, swinging her legs. the edge of an ax His voice had a sarcastic edge.
    [Show full text]
  • John Athayde and Bruce Williams — «The Rails View
    What readers are saying about The Rails View This is a must-read for Rails developers looking to juice up their skills for a world of web apps that increasingly includes mobile browsers and a lot more JavaScript. ➤ Yehuda Katz Driving force behind Rails 3.0 and Co-founder, Tilde In the past several years, I’ve been privileged to work with some of the world’s leading Rails developers. If asked to name the best view-layer Rails developer I’ve met, I’d have a hard time picking between two names: Bruce Williams and John Athayde. This book is a rare opportunity to look into the minds of two of the leading experts on an area that receives far too little attention. Read, apply, and reread. ➤ Chad Fowler VP Engineering, LivingSocial Finally! An authoritative and up-to-date guide to everything view-related in Rails 3. If you’re stabbing in the dark when putting together your Rails apps’ views, The Rails View provides a big confidence boost and shows how to get things done the right way. ➤ Peter Cooper Editor, Ruby Inside and Ruby Weekly The Rails view layer has always been a morass, but this book reins it in with details of how to build views as software, not just as markup. This book represents the wisdom gained from years’ worth of building maintainable interfaces by two of the best and brightest minds in our business. I have been writing Ruby code for over a decade and Rails code since its inception, and out of all the Ruby books I’ve read, I value this one the most.
    [Show full text]
  • Html Cheat Sheet
    BEGINNER’S_ ​ HTML CHEAT SHEET Main root 2 Document metadata 2 Sectioning root 3 Content sectioning 3 Text content 4 Inline text semantics 6 Image and multimedia 8 Scripting 9 Demarcating edits 9 Table content 9 Forms 11 Interactive elements 12 WebsiteSetup.org - Beginner’s HTML Cheat Sheet ​ 1 Main root <html> … </html> The HTML <html> element represents the root (top-level element) of an HTML document, so it is also referred to as the root element. All other elements must be descendants of this element. Example: <!DOCTYPE html> <html lang="en"> <head>...</head> <body>...</body> </html> Document metadata <head> … </head> The HTML <head> element contains machine-readable information (metadata) about the document, like its title, scripts, and style sheets. <link> The HTML External Resource Link element (<link>) specifies relationships between the current document and an external resource. This element is most commonly used to link to stylesheets, but is also used to establish site icons (both "favicon" style icons and icons for the home screen and apps on mobile devices) among other things. <meta> The HTML <meta> element represents metadata that cannot be represented by other HTML meta-related elements, like <base>, <link>, <script>, <style> or <title> <style> … </style> The HTML <style> element contains style information for a document, or part of a document. <title> … </title> The HTML Title element (<title>) defines the document's title that is shown in a browser's title bar or a page's tab. Example: WebsiteSetup.org - Beginner’s HTML Cheat Sheet ​ 2 <!DOCTYPE html> <html lang="en"> <head>...</head> <body>...</body> </html> Sectioning root <body> … </body> The HTML <body> Element represents the content of an HTML document.
    [Show full text]
  • Download Har File Viewer
    download har file viewer Download har file viewer. Если вы не знаете, как получить HAR-файл, ознакомьтесь с инструкцией на странице загрузки для трех самых распространенных браузеров: Chrome, Firefox и Internet Explorer. Нажмите кнопку выбора файла. Выберите HAR-файл для анализа. Воспользуйтесь ей, чтобы выбрать файл для анализа. Записи могут быть показаны вместе или с разбивкой по страницам. Временные метки записей в таблице могут быть относительными или абсолютными. В первом режиме метки, которые соответствуют каждой записи, располагаются на временной шкале обработки страницы, а во втором метка каждой записи занимает всю ширину столбца. Относительный режим используется только при группировке записей по страницам. – полезный инструмент, позволяющий выполнять сложный поиск в HAR-записях. Самый простой способ поиска – ввести несколько поисковых слов, например [получить диск]. В результате будут найдены записи, содержащие все эти слова в ответе и запросе. Обратите внимание, что словосочетания в кавычках обрабатываются как единый поисковый запрос, поэтому для запроса [неделя "количество событий"] будут показаны результаты, где есть фраза "количество событий". Кроме того, поисковые запросы могут быть представлены парами "поле – поисковая фраза", например [requst.url:поисковая_фраза request.method:поисковая_фраза response.status:поисковая_фраза]. Для более сложного поиска можно использовать операторы, создавать группы и указывать поля. Оператор влияет на непосредственно следующую за ним поисковую фразу, изменяя способ ее поиска в целой группе или запросе. Поддерживаемые операторы: & : оператор по умолчанию, выполняющий операцию AND для результатов следующего поискового запроса и результатов всех предыдущих операций. | : выполняет операцию OR для результатов следующего поискового запроса и результатов всех предыдущих операций. ^ : выполняет операцию XOR для результатов следующего поискового запроса и результатов всех предыдущих операций. - : исключает результаты следующего поискового запроса. Выберите HAR-файл.
    [Show full text]
  • Microdata 184 Cross-Document Messaging 187 Accessible Rich Internet Applications (ARIA) 188 Accessibility 188 in Conclusion 191
    Mobile HTML5 Estelle Weyl Mobile HTML5 by Estelle Weyl Copyright © 2014 Estelle Weyl. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/ institutional sales department: 800-998-9938 or [email protected]. Editors: Simon St. Laurent and Meghan Blanchette Indexer: Lucie Haskins Production Editor: Kristen Brown Cover Designer: Randy Comer Copyeditor: Kiel Van Horn Interior Designer: David Futato Proofreaders: Troy Mott and Jasmine Kwityn Illustrator: Rebecca Demarest November 2013: First Edition Revision History for the First Edition: 2013-11-12: First release See http://oreilly.com/catalog/errata.csp?isbn=9781449311414 for release details. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Mobile HTML5, the image of a Racket-tailed Drongo, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trade‐ mark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and author assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-1-449-31141-4 [LSI] Table of Contents Introduction.
    [Show full text]
  • HTML5 Cheatsheet 2019
    CHEAT SHEET HTML5 WEB DEVELOPMENT Created by @Manz ( https://twitter.com/Manz ) https://lenguajehtml.com/ S HTML Syntax Tag structure C Comment Syntax Dev annotations S Social metadata For social networks HTML TAG/ATTRIBUTE SYNTAX HTML COMMENT SYNTAX FACEBOOK OPEN GRAPH <tag attribute="value"> content </tag> <!-- text without effects on webpage --> <meta> metadata tag for open graph property metadata type open graph D Document tags HTML main structure H Head tags Header & document metadata content metadata value open graph MAIN TAGS RELATIONS REQUIRED METADATA PROPERTIES <!DOCTYPE html> HTML5 document <link> document relation og:title title of your object <html> document content root tag href link to related document og:type type of your object <head> metadata header related docs hreflang code doc language en, es... music video article book <body> page content visible content type mime hint type for browser profile website title set title to stylesheet set og:image image url for preview G Global Attributes for all elements sizes hint size for favicon 64x64, 96x96 og:url canonical & absolute url DOM / STYLE ATTRIBUTES rel relation type with other document OPTIONAL METADATA PROPERTIES id element identifier unique per page BASIC RELATION og:audio complementary audio url class element class multiple per page alternate link to alternate version og:description 1-2 sentence descr. slot element slot reference to <slot> author link to author URL og:determiner word auto, the, a, an, ... style inline CSS styles css properties help link to help URL
    [Show full text]
  • Web-Enabled DDS Version 1.0
    Date: July 2016 Web-Enabled DDS Version 1.0 __________________________________________________ OMG Document Number: formal/2016-03-01 Standard document URL: http://www.omg.org/spec/DDS-WEB Machine Consumable File(s): Normative: http://www.omg.org/spec/DDS-WEB/20150901/webdds_rest1.xsd http://www.omg.org/spec/DDS-WEB/20150901/webdds_websockets1.xsd http://www.omg.org/spec/DDS-WEB/20131122/webdds_soap1_types.xsd http://www.omg.org/spec/DDS-WEB/20131122/webdds_soap1.wsdl http://www.omg.org/spec/DDS-WEB/20131122/webdds_soap1_notify.wsdl Non-normative: http://www.omg.org/spec/DDS-WEB/20150901/webdds_rest1_example.xml http://www.omg.org/spec/DDS-WEB/20150901/webdds_pim_model_v1.eap _______________________________________________ Copyright © 2013, eProsima Copyright © 2016, Object Management Group, Inc. (OMG) Copyright © 2013, Real-Time Innovations, Inc. (RTI) Copyright © 2013, THALES USE OF SPECIFICATION - TERMS, CONDITIONS & NOTICES The material in this document details an Object Management Group specification in accordance with the terms, condi- tions and notices set forth below. This document does not represent a commitment to implement any portion of this speci- fication in any company's products. The information contained in this document is subject to change without notice. LICENSES The companies listed above have granted to the Object Management Group, Inc. (OMG) a nonexclusive, royalty-free, paid up, worldwide license to copy and distribute this document and to modify this document and distribute copies of the modified version. Each of the copyright holders listed above has agreed that no person shall be deemed to have infringed the copyright in the included material of any such copyright holder by reason of having used the specification set forth herein or having conformed any computer software to the specification.
    [Show full text]
  • Fido-Uaf-Client-Api-Transport-V1.0-Ps
    FIDO UAF Application API and Transport Binding Specification v1.0 FIDO Alliance Proposed Standard 08 December 2014 This version: https://fidoalliance.org/specs/fido-uaf-v1.0-ps-20141208/fido-uaf-client-api-transport-v1.0-ps-20141208.html Previous version: https://fidoalliance.org/specs/fido-uaf-client-api-transport-v1.0-rd-20141008.pdf Editor: Brad Hill, PayPal, Inc. Contributors: Davit Baghdasaryan, Nok Nok Labs, Inc. Bill Blanke, Nok Nok Labs, Inc. Dr. Rolf Lindemann, Nok Nok Labs, Inc. Jeff Hodges, PayPal, Inc. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2013-2014 FIDO Alliance All Rights Reserved. Abstract Describes APIs and an interoperability profile for client applications to utilize FIDO UAF. This includes methods of communicating with a FIDO UAF Client for both Web platform and Android applications, transport requirements, and an HTTPS interoperability profile for sending FIDO UAF messages to a compatible server. Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current FIDO Alliance publications and the latest revision of this technical report can be found in the FIDO Alliance specifications index at https://www.fidoalliance.org/specifications/. This document was published by the FIDO Alliance as a Proposed Standard. If you wish to make comments regarding this document, please Contact Us. All comments are welcome. Implementation of certain elements of this Specification may require licenses under third party intellectual property rights, including without limitation, patent rights.
    [Show full text]
  • Focus Styles
    Searching accessible components Sami Keijonen Recourses ● Guide to accessible components in Smashing Magazine. ● WAI-ARIA practises. ● Scott O’Haras accessible components. Components like (1/2) ● Focus styles ● Navigation ● Icon only components (social links) ● “Cards” (image, heading, text linking to article) ● Modal dialogs Components like (2/2) ● Accordion ● Tabs ● Styling checkboxes and radio buttons ● “Autocomplete” (dynamic search results) A11y Figma Kit ● A11y Figma Kit for inspiration and reminder. ○ Article explaining the a11y Figma Kit. ● Accessibility plugins for Figma. Focus styles ● All interactive elements (links, form elements etc.) should have focus styles. ○ Crucial for keyboard users. ● Remember to style focus styles in design process (not just hover). In WCAG 2.1 there is only color contrast 3:1 guideline. :focus { Focus styles outline: 0.25rem solid #222; } Color contrast? In 2.2 draft there are also guidelines for change of contrast and minimum area. Focus styles Note that if box-shadow is used, still use transparent outline for WIN high contrast mode. Good examples Never use :focus { outline: 0 } CSS :focus { box-shadow: ... outline: 0.25rem solid transparent; } :focus-visible is for that and now also Safari 14.1 supports it. // Base focus styles :focus { outline: 0.25em solid $color; Focus styles outline-offset: 0.25em; } What about when focus styles // Be careful to remove focus styles are triggered also using mouse // for “mouse” users. click? :focus:not(:focus-visible) { outline: none; More about focus styles. } <nav> <ul> Navigation <li><a href=”url”>Link 1</a></li> <li><a href=”url”>Link 2</a></li> </ul> Start with semantic markup </nav> Navigation <nav aria-label=”Main”> If there are several <ul> navigation, it’s good to add <li><a href=”url”>Link 1</a></li> name using aria-label <li><a href=”url”>Link 2</a></li> attribute.
    [Show full text]