In this two-part presentation, Russ will guide us on a deep dive into how to create accessible modals and accessible autocomplete search functions. Along the way, we will look at the problem for different types of users as well as explore how ARIA can be used to improve these experiences. There will be blood, sweat and tears (Russ' words!) but hopefully a happy outcome for all.
Presentation for the Sydney Web Accessibility & Inclusive Design - 30 August 2019
This presentation was fro the AllyBtyes event on 21 May 2020. The presentations looks at a pattern for building or reviewing any new UI component – semantics, focusable, keyboard interaction, visible states, accessible name and relationships.
What are accessible names and why should you care?Russ Weakley
This presentation will look at accessible names, how they are exposed in the browsers accessibility tree, and their importance to assistive technologies. There will be a deep dive into simple examples, advanced examples using ARIA, and an overview of the W3C's Accessible Name and Description Computation.
The document discusses user interface states and provides examples of how states can be systematically defined across different UI components. It defines what states are and provides examples like visited, focus, hover, active, disabled, invalid, checked/selected states. It emphasizes the importance of defining states for all interactive elements, including custom elements, to ensure usability. It also stresses the importance of maintaining consistent state styling across a design system through the use of a state table that defines how each state should appear for different common UI elements like links, buttons, forms, tabs etc. This helps establish visual consistency and maintainability.
Accessibility in Design systems - the pain and gloryRuss Weakley
Slides from CodeHeart Design 2018: Building a design system is a painful enough, but how do you add accessibility into the mix? Is it an "up-at-dawn, pride-swallowing siege", or can it become part of the normal work flow. We'll look at accessibility for different roles - such as UX, UI and devs, as well as where accessibility should be injected into the process.
This document discusses making inline error messages accessible for assistive technologies like screen readers. It provides 4 methods for programmatically associating error messages with form fields: 1) wrapping the label, 2) using aria-describedby, 3) aria-labelledby, and 4) the newer aria-errormessage. It also recommends using aria-invalid to indicate the validation state and aria-live to announce changes for screen reader users. The goal is to ensure error messages are announced and read aloud as part of the form interaction for assistive technology users.
The document discusses several methods for programmatically associating inline error messages and hints with form fields to ensure they are accessible to screen reader users. It describes wrapping form fields and messages in <label> tags, using aria-describedby to link them, and aria-errormessage as recommended by WAI-ARIA. For longer hints, it suggests using pop-up tooltips but ensuring they are accessible via keyboard by only showing on focus, hover or active states. The tooltip content should be directly associated with the relevant form field for maximum accessibility.
Accessible custom radio buttons and checkboxesRuss Weakley
Creating custom-designed radio buttons and checkboxes has never been easy. Many developers have found ways of hacking these elements using CSS and JavaScript. but can they also be accessible. The answer is yes, with a little extra effort. This presentation will walk through some simple examples to show how radio buttons and checkboxes can be semantic as well as keyboard/screen-reader accessible.
This talk will look at a range of common application components and how they can be made accessible - quickly and easily - for all users. We'll look at how to notify users when changing the DOM after page load. We will also look in-depth at accessible form validation, modal windows and adding additional information for screen reader users.
This presentation was fro the AllyBtyes event on 21 May 2020. The presentations looks at a pattern for building or reviewing any new UI component – semantics, focusable, keyboard interaction, visible states, accessible name and relationships.
What are accessible names and why should you care?Russ Weakley
This presentation will look at accessible names, how they are exposed in the browsers accessibility tree, and their importance to assistive technologies. There will be a deep dive into simple examples, advanced examples using ARIA, and an overview of the W3C's Accessible Name and Description Computation.
The document discusses user interface states and provides examples of how states can be systematically defined across different UI components. It defines what states are and provides examples like visited, focus, hover, active, disabled, invalid, checked/selected states. It emphasizes the importance of defining states for all interactive elements, including custom elements, to ensure usability. It also stresses the importance of maintaining consistent state styling across a design system through the use of a state table that defines how each state should appear for different common UI elements like links, buttons, forms, tabs etc. This helps establish visual consistency and maintainability.
Accessibility in Design systems - the pain and gloryRuss Weakley
Slides from CodeHeart Design 2018: Building a design system is a painful enough, but how do you add accessibility into the mix? Is it an "up-at-dawn, pride-swallowing siege", or can it become part of the normal work flow. We'll look at accessibility for different roles - such as UX, UI and devs, as well as where accessibility should be injected into the process.
This document discusses making inline error messages accessible for assistive technologies like screen readers. It provides 4 methods for programmatically associating error messages with form fields: 1) wrapping the label, 2) using aria-describedby, 3) aria-labelledby, and 4) the newer aria-errormessage. It also recommends using aria-invalid to indicate the validation state and aria-live to announce changes for screen reader users. The goal is to ensure error messages are announced and read aloud as part of the form interaction for assistive technology users.
The document discusses several methods for programmatically associating inline error messages and hints with form fields to ensure they are accessible to screen reader users. It describes wrapping form fields and messages in <label> tags, using aria-describedby to link them, and aria-errormessage as recommended by WAI-ARIA. For longer hints, it suggests using pop-up tooltips but ensuring they are accessible via keyboard by only showing on focus, hover or active states. The tooltip content should be directly associated with the relevant form field for maximum accessibility.
Accessible custom radio buttons and checkboxesRuss Weakley
Creating custom-designed radio buttons and checkboxes has never been easy. Many developers have found ways of hacking these elements using CSS and JavaScript. but can they also be accessible. The answer is yes, with a little extra effort. This presentation will walk through some simple examples to show how radio buttons and checkboxes can be semantic as well as keyboard/screen-reader accessible.
This talk will look at a range of common application components and how they can be made accessible - quickly and easily - for all users. We'll look at how to notify users when changing the DOM after page load. We will also look in-depth at accessible form validation, modal windows and adding additional information for screen reader users.
The document discusses guidelines for making modal windows accessible. A modal window forces user interaction before allowing interaction with the main page. Key guidelines include: allowing full keyboard and screen reader navigation within the modal; informing users and screen readers when a modal opens through focus, labels, roles and descriptions; preventing interaction outside the modal; and ensuring screen readers can operate in "read" and "form" modes within modals as needed.
Building accessible web components without tearsRuss Weakley
Slides from #Respond16, Sydney Melbourne 2016
So, you've built an amazing new web application. It uses all the latest frameworks and libraries. It's beautiful to behold.
But is it accessible? Many web applications these days are built on top of pre-existing frameworks or code bases and there is little thought to how well these components will work for different assistive devices.
This talk will look at a range of common application components and how they can be made accessible - quickly and easily - for all users. We'll look at how to notify users when changing the DOM after page load. We will also look in-depth at accessible form validation, modal windows, drop-down menus, in-page tabs and other commonly used we components. You will leave this talk ready and eager to enhance your application, and in the process, make it available to entirely new audiences.
aria-live: the good, the bad and the uglyRuss Weakley
Almost all web sites and web applications today are heavily reliant on JavaScript to provide rich interactions for the user. But how can we make these interactions accessible for assistive technologies such as screen readers? The answer is WAI-ARIA – and in many cases, the aria-live property. The presentation will explore the use of WAI-ARIA and the aria-live property to alert screen readers to changes in the DOM. The presentation will also look at support for aria-live across various screen readers and how the property can be most effectively used today.
This presentation for Inclusive Design 24 (#ID24) explores how to create accessible, usable "floating" labels. Floating labels are where the label moves above form controls based on user interaction.
The document discusses various types of user interfaces in Android. It describes the view hierarchy in Android using ViewGroups and Views as the basic building blocks. It explains common layouts like LinearLayout, RelativeLayout, TableLayout, GridLayout and ListView that can be used to arrange views. Key classes involved include View, ViewGroup, and different view subclasses that serve as widgets. The document also compares Java and Android approaches to designing user interfaces.
The document discusses creating and working with web forms in HTML, including adding different form elements like input boxes, radio buttons, drop-down lists, checkboxes, and text areas. It also covers setting attributes of forms and form elements, organizing fields using fieldsets, linking labels to fields, and submitting forms using buttons. The last few sections discuss hidden fields, specifying actions and methods for forms, and designing custom buttons.
UI layouts define the structure and organization of elements in an Android activity's user interface. There are two main options for declaring layouts: in XML files or programmatically in Java code. Common layout types include LinearLayout, RelativeLayout, TableLayout, and FrameLayout. Layout files use a tree structure with attributes like ID, width, height, and weight to position child views. This allows separation of UI design from activity code.
1. The document provides steps to create a quiz game using multiple forms in Visual Basic 6.0, including creating interfaces and coding the logic for each form.
2. It describes creating 5 forms - a login form, loading form, two question forms, and a results form.
3. Coding instructions are provided for each form to control navigation between forms and track the score as the user answers questions.
The document discusses HTML forms and form elements. It provides objectives and descriptions of how to create forms using HTML tags like <form> and <input>. It explains various form elements including text fields, password fields, text areas, drop-down menus, checkboxes, radio buttons, and their attributes. The document provides examples of code for each form element.
The document discusses various features of the Visual Basic Editor in Microsoft Office, including:
1. It describes how to open the Visual Basic Editor from within Word or other Office applications using keyboard shortcuts or menu options.
2. It outlines the main windows of the Visual Basic Editor, including the Project Explorer, Code window, and Object Browser.
3. It provides details on features like Auto List Members, Quick Info, and List Constants that help provide information about code as you work.
UML Interview Questions
Unified Modeling Language (UML) is a standard language for designing and documenting a system in an object-oriented manner. It has nine diagrams which can be used in design documents to express the design of a software architecture. Use case diagrams depict what a system does from the user's perspective and answer "What will the system do?". They show actors, use cases, and scenarios. Class diagrams represent the static structure of a project by showing classes, attributes, methods, and relationships between classes like associations, generalization, and dependencies. Sequence diagrams show the interaction between objects over time by depicting messages passed between objects.
The document provides an introduction to HTML frames. It explains that frames divide the browser window into separate panes, each displaying a different HTML document. The <frameset> tag is used to define rows and columns to divide the window, while <frame> tags specify the HTML documents to display in each frame. Attributes like rows, cols, border, and frameborder control the layout and appearance of frames. The <noframes> tag provides content for browsers that do not support frames.
The document describes the Form namespace and Form.Element module in Prototype.js, which provide methods for manipulating and serializing form data. The Form namespace allows disabling/enabling an entire form, finding/focusing the first form element, and serializing all form data. The Form.Element module provides methods for individual form controls, like getting/setting values, disabling/enabling, and serializing a single element. These methods allow programmatic manipulation of forms for tasks like validation, submission, and pre-filling values.
The document discusses HTML frames and their usage. It defines frames as dividing the browser window into separate sections, each displaying a different HTML document. It describes the key tags used to create frames - <frameset> divides the window and defines rows and columns, <frame> specifies the HTML document to display in each frame section. It also covers attributes like src, name, and frameborder. Frames allow reloading single panes without reloading the whole page but can cause printing and compatibility issues.
This document discusses inbound and outbound plugs in SAPUI5, which are used for navigation and data transfer between views. It provides an example of using outbound and inbound plugs to navigate from an items list view to a product details view when a product is clicked, and pass the selected product entity between the views. The outbound plug on the items list view passes the product to the inbound plug on the product details view via a shared collection attribute, displaying the correct product details.
The document discusses different types of views and view groups in Android user interface development. It describes layouts like LinearLayout, RelativeLayout and FrameLayout that extend the ViewGroup class. These layouts allow arranging views in different orientations using attributes like layout_width, layout_height, layout_weight etc. The document also talks about defining views and layouts in XML files or programmatically at runtime.
Front End Frameworks - are they accessibleRuss Weakley
Frameworks like Bootstrap provide accessibility benefits but also risks if not implemented correctly. Common issues include non-semantic elements styled as buttons or headings, confusing screen reader users. Frameworks also may not fully explain interactive elements like dropdowns and modals. Developers must understand fundamentals of accessibility and not rely solely on frameworks being accessible "out of the box".
This document discusses steps to customize a Microsoft Access database for use as an application. It describes hiding unnecessary menu options, adding help text and tooltips, setting a startup form, creating a switchboard form for navigation, and adding security features like encryption and user permissions. Finally, it covers publishing the database or forms to the web by saving objects as static HTML files or dynamic web applications.
The document discusses guidelines for making modal windows accessible. A modal window forces user interaction before allowing interaction with the main page. Key guidelines include: allowing full keyboard and screen reader navigation within the modal; informing users and screen readers when a modal opens through focus, labels, roles and descriptions; preventing interaction outside the modal; and ensuring screen readers can operate in "read" and "form" modes within modals as needed.
Building accessible web components without tearsRuss Weakley
Slides from #Respond16, Sydney Melbourne 2016
So, you've built an amazing new web application. It uses all the latest frameworks and libraries. It's beautiful to behold.
But is it accessible? Many web applications these days are built on top of pre-existing frameworks or code bases and there is little thought to how well these components will work for different assistive devices.
This talk will look at a range of common application components and how they can be made accessible - quickly and easily - for all users. We'll look at how to notify users when changing the DOM after page load. We will also look in-depth at accessible form validation, modal windows, drop-down menus, in-page tabs and other commonly used we components. You will leave this talk ready and eager to enhance your application, and in the process, make it available to entirely new audiences.
aria-live: the good, the bad and the uglyRuss Weakley
Almost all web sites and web applications today are heavily reliant on JavaScript to provide rich interactions for the user. But how can we make these interactions accessible for assistive technologies such as screen readers? The answer is WAI-ARIA – and in many cases, the aria-live property. The presentation will explore the use of WAI-ARIA and the aria-live property to alert screen readers to changes in the DOM. The presentation will also look at support for aria-live across various screen readers and how the property can be most effectively used today.
This presentation for Inclusive Design 24 (#ID24) explores how to create accessible, usable "floating" labels. Floating labels are where the label moves above form controls based on user interaction.
The document discusses various types of user interfaces in Android. It describes the view hierarchy in Android using ViewGroups and Views as the basic building blocks. It explains common layouts like LinearLayout, RelativeLayout, TableLayout, GridLayout and ListView that can be used to arrange views. Key classes involved include View, ViewGroup, and different view subclasses that serve as widgets. The document also compares Java and Android approaches to designing user interfaces.
The document discusses creating and working with web forms in HTML, including adding different form elements like input boxes, radio buttons, drop-down lists, checkboxes, and text areas. It also covers setting attributes of forms and form elements, organizing fields using fieldsets, linking labels to fields, and submitting forms using buttons. The last few sections discuss hidden fields, specifying actions and methods for forms, and designing custom buttons.
UI layouts define the structure and organization of elements in an Android activity's user interface. There are two main options for declaring layouts: in XML files or programmatically in Java code. Common layout types include LinearLayout, RelativeLayout, TableLayout, and FrameLayout. Layout files use a tree structure with attributes like ID, width, height, and weight to position child views. This allows separation of UI design from activity code.
1. The document provides steps to create a quiz game using multiple forms in Visual Basic 6.0, including creating interfaces and coding the logic for each form.
2. It describes creating 5 forms - a login form, loading form, two question forms, and a results form.
3. Coding instructions are provided for each form to control navigation between forms and track the score as the user answers questions.
The document discusses HTML forms and form elements. It provides objectives and descriptions of how to create forms using HTML tags like <form> and <input>. It explains various form elements including text fields, password fields, text areas, drop-down menus, checkboxes, radio buttons, and their attributes. The document provides examples of code for each form element.
The document discusses various features of the Visual Basic Editor in Microsoft Office, including:
1. It describes how to open the Visual Basic Editor from within Word or other Office applications using keyboard shortcuts or menu options.
2. It outlines the main windows of the Visual Basic Editor, including the Project Explorer, Code window, and Object Browser.
3. It provides details on features like Auto List Members, Quick Info, and List Constants that help provide information about code as you work.
UML Interview Questions
Unified Modeling Language (UML) is a standard language for designing and documenting a system in an object-oriented manner. It has nine diagrams which can be used in design documents to express the design of a software architecture. Use case diagrams depict what a system does from the user's perspective and answer "What will the system do?". They show actors, use cases, and scenarios. Class diagrams represent the static structure of a project by showing classes, attributes, methods, and relationships between classes like associations, generalization, and dependencies. Sequence diagrams show the interaction between objects over time by depicting messages passed between objects.
The document provides an introduction to HTML frames. It explains that frames divide the browser window into separate panes, each displaying a different HTML document. The <frameset> tag is used to define rows and columns to divide the window, while <frame> tags specify the HTML documents to display in each frame. Attributes like rows, cols, border, and frameborder control the layout and appearance of frames. The <noframes> tag provides content for browsers that do not support frames.
The document describes the Form namespace and Form.Element module in Prototype.js, which provide methods for manipulating and serializing form data. The Form namespace allows disabling/enabling an entire form, finding/focusing the first form element, and serializing all form data. The Form.Element module provides methods for individual form controls, like getting/setting values, disabling/enabling, and serializing a single element. These methods allow programmatic manipulation of forms for tasks like validation, submission, and pre-filling values.
The document discusses HTML frames and their usage. It defines frames as dividing the browser window into separate sections, each displaying a different HTML document. It describes the key tags used to create frames - <frameset> divides the window and defines rows and columns, <frame> specifies the HTML document to display in each frame section. It also covers attributes like src, name, and frameborder. Frames allow reloading single panes without reloading the whole page but can cause printing and compatibility issues.
This document discusses inbound and outbound plugs in SAPUI5, which are used for navigation and data transfer between views. It provides an example of using outbound and inbound plugs to navigate from an items list view to a product details view when a product is clicked, and pass the selected product entity between the views. The outbound plug on the items list view passes the product to the inbound plug on the product details view via a shared collection attribute, displaying the correct product details.
The document discusses different types of views and view groups in Android user interface development. It describes layouts like LinearLayout, RelativeLayout and FrameLayout that extend the ViewGroup class. These layouts allow arranging views in different orientations using attributes like layout_width, layout_height, layout_weight etc. The document also talks about defining views and layouts in XML files or programmatically at runtime.
Front End Frameworks - are they accessibleRuss Weakley
Frameworks like Bootstrap provide accessibility benefits but also risks if not implemented correctly. Common issues include non-semantic elements styled as buttons or headings, confusing screen reader users. Frameworks also may not fully explain interactive elements like dropdowns and modals. Developers must understand fundamentals of accessibility and not rely solely on frameworks being accessible "out of the box".
This document discusses steps to customize a Microsoft Access database for use as an application. It describes hiding unnecessary menu options, adding help text and tooltips, setting a startup form, creating a switchboard form for navigation, and adding security features like encryption and user permissions. Finally, it covers publishing the database or forms to the web by saving objects as static HTML files or dynamic web applications.
The document discusses various tools in Excel for auditing and reviewing spreadsheets. It describes direct auditing tools like the Auditing Toolbar, Go To Tools, and keyboard shortcuts that allow tracing formulas and errors. Indirect methods include data validation, conditional formatting, and setting calculation and view options. Examples are provided for using the Auditing Toolbar icons, Go To Special, conditional formatting formulas, and setting calculation and view options to improve spreadsheet accuracy and productivity.
IBM Watson Analytics sets powerful analytics capabilities free so practically anyone can use them. Automated data preparation, predictive analytics, reporting, dashboards, visualization and collaboration capabilities, enable you to take control of your own analysis. You can then take the appropriate action to address a problem or seize an opportunity, all without asking IT or a data expert for help.
The document discusses interfacing with end users in ASP.NET. It provides two programming models - Web Forms and WCF Services. Web Forms enables creating user interfaces and application logic, while WCF Services enables remote server-side functionality access. It also discusses creating a basic web form in ASP.NET that displays the current date and time when a button is clicked to demonstrate the Web Forms model. Common controls like labels, textboxes, buttons are also summarized with their properties and events.
The document discusses various controls available in Windows Presentation Foundation (WPF) for building user interfaces. It describes standard controls like grids, labels, buttons, editors, lists, menus and toolbars. It also covers other controls like tooltips, borders, popups, frames and ranges. Specific controls like grid, label, buttons, editors, lists, menus and toolbars are discussed in more detail. The document also discusses dialog boxes, third-party controls and some other controls like calendar, date picker, image and popup.
CIS 3100 - Database Design and ImplementationProducts on Sale Da.docxmccormicknadine86
CIS 3100 - Database Design and Implementation
Products on Sale Database for Kahdea Inc.
1. Project Overview
The activities in this project are designed to provide a better understanding of how data is organized into a relational database. A relational database enables management information systems to support inventory, transactions and business intelligence capabilities.
Using Microsoft Access 2016, you will create and manage tables, perform data imports, link tables via relationships, create queries and finally create reports for executive summary.
A general overview of relational database fundamentals and Microsoft Access training via Lynda.com is provided in section 11 to enable your success in this project. Please allow enough time to expose yourself to this material before starting the project.
2. Company Background
Kahdea Inc. is a small startup company that sells sports merchandise online. The mission of the company is to successfully sell and deliver sports products for all. The company sells products for a wide variety of sports including football, basketball, baseball, soccer, hockey, and volleyball.
Kahdea is composed of twenty-eight (28) employees who work in different departments (production, operations, automation, accounting, human resources, finance, marketing, etc.). During their probation period, all employees are trained before being assigned into their positions.
Kahdea is planning to have their annual sale next month. This sale is an important event for the company because it can typically generate 31% of Kahdea’s annual revenue. The company has been planning this sale for some time now, and wants to make sure all transactions are supported without issue.
Your specific role in the project
You are a new hire at Kahdea. During your training, you are expected to learn about building and maintaining relational databases using Microsoft Access. The database you will support is being used to keep track of Kahdea’s sales during this period. Although the database has been constructed, the team needs your assistance inserting data, using forms, creating queries and reports.
Your first training task requires you to watch the Microsoft Access training videos on Lynda.com. A series of hyperlinks for reference information are provided for you at the end of this project document.
After you become familiar with Microsoft Access, open the Kahdea.accdb file.
3. Create a Table
Before you begin, the team wants to ensure you understand table structure. They would like you to create a table for Employees and populate a few records. The table should include the field names: EmployeeID(PK), Last Name, First Name, Phone and Attachments.
· Step 1: Click the “Create” tab on the top ribbon and select “Table Design”.
· Step 2: Enter the Field Names and Data Type. Include a Primary Key (EmployeeID) for
the table. Select attachment as the data type for the Attachments field.
· Step 3: Save the table as “Employee”.
· Step 4: Ent ...
- Database Design and ImplementationProducts on Sale Database fo.docxgertrudebellgrove
- Database Design and Implementation
Products on Sale Database for Kahdea Inc.
1. Project Overview
The activities in this project are designed to provide a better understanding of how data is organized into a relational database. A relational database enables management information systems to support inventory, transactions and business intelligence capabilities.
Using Microsoft Access 2016, you will create and manage tables, perform data imports, link tables via relationships, create queries and finally create reports for executive summary.
A general overview of relational database fundamentals and Microsoft Access training via Lynda.com is provided in section 11 to enable your success in this project. Please allow enough time to expose yourself to this material before starting the project.
2. Company Background
Kahdea Inc. is a small startup company that sells sports merchandise online. The mission of the company is to successfully sell and deliver sports products for all. The company sells products for a wide variety of sports including football, basketball, baseball, soccer, hockey, and volleyball.
Kahdea is composed of twenty-eight (28) employees who work in different departments (production, operations, automation, accounting, human resources, finance, marketing, etc.). During their probation period, all employees are trained before being assigned into their positions.
Kahdea is planning to have their annual sale next month. This sale is an important event for the company because it can typically generate 31% of Kahdea’s annual revenue. The company has been planning this sale for some time now, and wants to make sure all transactions are supported without issue.
Your specific role in the project
You are a new hire at Kahdea. During your training, you are expected to learn about building and maintaining relational databases using Microsoft Access. The database you will support is being used to keep track of Kahdea’s sales during this period. Although the database has been constructed, the team needs your assistance inserting data, using forms, creating queries and reports.
Your first training task requires you to watch the Microsoft Access training videos on Lynda.com. A series of hyperlinks for reference information are provided for you at the end of this project document.
After you become familiar with Microsoft Access, open the Kahdea.accdb file.
3. Create a Table
Before you begin, the team wants to ensure you understand table structure. They would like you to create a table for Employees and populate a few records. The table should include the field names: EmployeeID(PK), Last Name, First Name, Phone and Attachments.
· Step 1: Click the “Create” tab on the top ribbon and select “Table Design”.
· Step 2: Enter the Field Names and Data Type. Include a Primary Key (EmployeeID) for
the table. Select attachment as the data type for the Attachments field.
· Step 3: Save the table as “Employee”.
· Step 4: Enter the ...
Dialogs in Android are small windows that prompt users to take an action or enter information before proceeding. There are several types of dialogs including alerts, popups, and toasts. Alerts inform users and require a response while popups require a single selection. Toasts provide lightweight feedback. The example shows how to create an alert dialog using a Builder pattern to set the message, buttons, and listeners.
Create a basic performance point dashboard epcEPC Group
This document provides instructions for creating a basic PerformancePoint dashboard with three key elements:
1) It describes creating a simple dashboard that contains a scorecard, an analytic grid report, and a filter.
2) It orients the user to the Dashboard Designer user interface which is divided into four main areas: the ribbon, workspace browser, center pane, and details pane.
3) It guides the user through creating the dashboard items - selecting a data source, creating an analytic grid report to display data from the source, selecting or creating KPIs, and then generating a scorecard and filter to populate the new dashboard.
The document provides information on various features of MicroStrategy Desktop including:
- The History folder stores metadata about report execution requests and scheduled reports.
- Personal and Public Objects folders contain user and shared reports, documents, and other objects.
- Reports can be created by dragging attributes and metrics onto the report canvas and customizing layout, formatting, and filters.
- Features like drilling, pivoting, sorting, outlining, and formatting can manipulate data visualization.
- Templates define common report layouts that can be customized. Filters restrict data based on attributes.
- Metrics perform calculations on data and can be simple or derived. Prompts allow filtering reports interactively.
This document provides an overview of WinForms GUI programming in .NET. It discusses how event-driven programming works in WinForms applications and how Visual Studio supports drag-and-drop design of WinForms. It also describes some key concepts like forms, controls, properties and events. The document explains how to set up a basic WinForms application and interact with common controls like labels, text boxes and buttons.
The document discusses multiple document interface (MDI) windows in Visual C# .NET. Some key points:
1) MDI programs allow users to edit multiple documents at once, with each document in its own child window contained within the parent application window.
2) Only one child window can be active at a time. Child windows cannot be moved outside the parent window.
3) To create an MDI application, set the parent form's IsMDIContainer property to True, create child forms, and set each child's MdiParent property to the parent form.
This document provides instructions for disabling or hiding administrative tools in Windows 8.1 through three methods:
1) Enabling the display of administrative tools in the Start Screen search.
2) Using the Group Policy Editor to hide specific Control Panel items, including administrative tools.
3) Modifying the registry to disable administrative tools.
It also describes denying standard users access to the Administrative Tools menu folder.
Product Supplier:
59,58,8,2.50
CIS 3100 - Database Design and Implementation
Scoring Rubric
Criteria
Points Possible
Points Earned
A. Employee Table
1. Table & data types created correctly
2. Records / attributes populated correctly
(5)
(5)
10
B. Import Data
1. Customer data imported correctly
2. Product Supplier data imported correctly
(5)
(5)
10
C. Forms
1. Supplier form is functional
2. Product Category form is functional
(5)
(5)
10
D. Relationships
1. Relationships are properly configured
(20)
20
E. Queries
1. MostProductsSold query is functional
2. CustomerOrders query is functional
3. ProductPrices query is functional
(10)
(10)
(10)
30
F. Report
1. Report meets management expectations
(10)
10
G. Assessment
1. Assessment meets management expectations
2. Assessment embedded in personal record
(5)
(5)
10
Total
100
CIS 3100 - Database Design and Implementation
Products on Sale Database for Kahdea Inc.
1. Project Overview
The activities in this project are designed to provide a better understanding of how data is organized into a relational database. A relational database enables management information systems to support inventory, transactions and business intelligence capabilities.
Using Microsoft Access 2016, you will create and manage tables, perform data imports, link tables via relationships, create queries and finally create reports for executive summary.
A general overview of relational database fundamentals and Microsoft Access training via Lynda.com is provided in section 11 to enable your success in this project. Please allow enough time to expose yourself to this material before starting the project.
2. Company Background
Kahdea Inc. is a small startup company that sells sports merchandise online. The mission of the company is to successfully sell and deliver sports products for all. The company sells products for a wide variety of sports including football, basketball, baseball, soccer, hockey, and volleyball.
Kahdea is composed of twenty-eight (28) employees who work in different departments (production, operations, automation, accounting, human resources, finance, marketing, etc.). During their probation period, all employees are trained before being assigned into their positions.
Kahdea is planning to have their annual sale next month. This sale is an important event for the company because it can typically generate 31% of Kahdea’s annual revenue. The company has been planning this sale for some time now, and wants to make sure all transactions are supported without issue.
Your specific role in the project
You are a new hire at Kahdea. During your training, you are expected to learn about building and maintaining relational databases using Microsoft Access. The database you will support is being used to keep track of Kah ...
Dynamics CRM 2013: Create or customize dashboardsVinh Nguyen
Dynamics CRM 2013: Create or customize dashboards
If you need to find a perfect solution for your business or should you have any questions please do not hesitate to contact Think Next
Website: http://www.thinknext.vn
Forum: http://www.thinknext.vn/diendan/index.php?threads/dynamics-crm-create-or-customize-dashboards.464/
The document provides tips and instructions for getting the most out of Lotus Notes by utilizing features like shortcuts, bookmarks, searching, widgets, and actions. It discusses how to customize the Notes interface through bookmarks and widgets, efficiently search emails and calendars, and add interactivity to widgets using actions. Specific instructions are given for adding widgets like Google gadgets and mail views to the Notes sidebar.
Similaire à Creating accessible modals and autocompletes (20)
This presentation will look at how to build accessible chat windows. Along the way we will explore: how they differ from traditional modals, how to manage focus, how to manage dynamically updating content for assistive technologies and more. The session is designed for developers and coders.
This presentation for AllyCamp 2020, looks at accessible names, how they are exposed in the browsers accessibility tree, and their importance to assistive technologies. There is also a deep dive into simple examples, advanced examples using ARIA, and an overview of the W3C's Accessible Name and Description Computation.
What is WCAG 2 and why should we care?Russ Weakley
A presentation for IAG staff for the "Future is here" event on 6 May 20202. This presentation covers three topics - "What are our legal responsibilities around accessibility?", "What is WCAG?", and "What is inclusive design?"
Building an accessible progressive loaderRuss Weakley
This presentation for A11y Bytes May 2019, takes you through how to mark up a progress loader using the progress element. Then, eight tips for making the progress loader accessible.
This presentation covers; different types of disabilities, assistive technologies, legal and ethical responsibilities as well as a range of terms such as W3C, WAI and WCAG.
In the old days, many developers looked at complex websites and web applications as a series of individual pages. These days, it’s all about abstracting these pages down to re-usable elements, modules and components which are then documented, designed and built as comprehensive pattern libraries. Pattern libraries can be used as an integral part of the UX, design and front-end development phases. But where should accessibility be included in these different types of pattern libraries? Come on a journey as we explore the pain and glory of baking accessibility into UX, design and front-end pattern libraries.
In the old days, many developers looked at complex websites and web applications as a series of individual pages. These days, it’s all about abstracting these pages down to re-usable elements, modules and components which are then documented, designed and built as comprehensive pattern libraries. Pattern libraries can be used as an integral part of the UX, design and front-end development phases. But where should accessibility be included in these different types of pattern libraries? Come on a journey as we explore the pain and glory of baking accessibility into UX, design and front-end pattern libraries.
Building an accessible auto-complete - #ID24Russ Weakley
This presentation will take a deep dive into how to create an auto-complete search function that is accessible to a range of different users including keyboard-only and screen reader users. Along the way, we will explore important keystrokes and aria attributes that can be used enhance the experience for all users.
The document provides guidance on creating accessible autocomplete search functionality. It discusses user experience considerations like clear labeling and instructions. It also covers keyboard support, ensuring all actions can be performed via keyboard. The document outlines how to add appropriate markup for screen readers, including labels, roles, properties to describe interactions and options. Code examples are provided for the overall structure and specific elements.
Creating a Simple, Accessible On/Off SwitchRuss Weakley
Have you ever tried to style checkboxes or radio buttons and ended up pulling your hair out? This presentation will explore a few simple tricks that can be used to style checkboxes and radio buttons. In this case, we will make them look like an on/off switch.
At first glance, CSS line-height seems very simple, but there is a lot going on below the surface. Line-height is important for any designer or front end developer to understand as it can impact almost every aspect of our layouts.
Understanding the mysteries of the CSS property value syntaxRuss Weakley
This presentation will reveal the wonders of the W3C CSS property and value syntax. Along the way we will explore the mysterious double pipes, pound signs, double ampersands and more. You will come away a CSS syntax expert, able to understand any CSS property / value syntax no matter how complex... or your money back!
This document discusses the evolution of roles in UX/UI design and development over time. It presents a brief history starting in the 1990s with webmasters and designers focused on HTML. By the late 1990s, developers also worked with HTML and usability/UX emerged. The roles continued to expand and combine skills, with modern practitioners often working across UX research, interaction design, visual design, front-end development, and considerations for accessibility. The document suggests that while specialization can be valuable, it is also beneficial for those in UX to learn some front-end development skills to enable quick prototyping and understand rich interactions and responsive design.
This document discusses best practices for creating CSS pattern libraries. It recommends starting with the smallest reusable components and building up to larger page-level templates. Key aspects covered include using a naming convention based on modules, modifiers and descendants; avoiding overly specific class names; and including utility classes to add single styles without new classes. The document also provides examples of how to structure and name classes for common interface patterns.
How to Fix the Import Error in the Odoo 17Celine George
An import error occurs when a program fails to import a module or library, disrupting its execution. In languages like Python, this issue arises when the specified module cannot be found or accessed, hindering the program's functionality. Resolving import errors is crucial for maintaining smooth software operation and uninterrupted development processes.
Reimagining Your Library Space: How to Increase the Vibes in Your Library No ...Diana Rendina
Librarians are leading the way in creating future-ready citizens – now we need to update our spaces to match. In this session, attendees will get inspiration for transforming their library spaces. You’ll learn how to survey students and patrons, create a focus group, and use design thinking to brainstorm ideas for your space. We’ll discuss budget friendly ways to change your space as well as how to find funding. No matter where you’re at, you’ll find ideas for reimagining your space in this session.
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
A workshop hosted by the South African Journal of Science aimed at postgraduate students and early career researchers with little or no experience in writing and publishing journal articles.
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
LAND USE LAND COVER AND NDVI OF MIRZAPUR DISTRICT, UPRAHUL
This Dissertation explores the particular circumstances of Mirzapur, a region located in the
core of India. Mirzapur, with its varied terrains and abundant biodiversity, offers an optimal
environment for investigating the changes in vegetation cover dynamics. Our study utilizes
advanced technologies such as GIS (Geographic Information Systems) and Remote sensing to
analyze the transformations that have taken place over the course of a decade.
The complex relationship between human activities and the environment has been the focus
of extensive research and worry. As the global community grapples with swift urbanization,
population expansion, and economic progress, the effects on natural ecosystems are becoming
more evident. A crucial element of this impact is the alteration of vegetation cover, which plays a
significant role in maintaining the ecological equilibrium of our planet.Land serves as the foundation for all human activities and provides the necessary materials for
these activities. As the most crucial natural resource, its utilization by humans results in different
'Land uses,' which are determined by both human activities and the physical characteristics of the
land.
The utilization of land is impacted by human needs and environmental factors. In countries
like India, rapid population growth and the emphasis on extensive resource exploitation can lead
to significant land degradation, adversely affecting the region's land cover.
Therefore, human intervention has significantly influenced land use patterns over many
centuries, evolving its structure over time and space. In the present era, these changes have
accelerated due to factors such as agriculture and urbanization. Information regarding land use and
cover is essential for various planning and management tasks related to the Earth's surface,
providing crucial environmental data for scientific, resource management, policy purposes, and
diverse human activities.
Accurate understanding of land use and cover is imperative for the development planning
of any area. Consequently, a wide range of professionals, including earth system scientists, land
and water managers, and urban planners, are interested in obtaining data on land use and cover
changes, conversion trends, and other related patterns. The spatial dimensions of land use and
cover support policymakers and scientists in making well-informed decisions, as alterations in
these patterns indicate shifts in economic and social conditions. Monitoring such changes with the
help of Advanced technologies like Remote Sensing and Geographic Information Systems is
crucial for coordinated efforts across different administrative levels. Advanced technologies like
Remote Sensing and Geographic Information Systems
9
Changes in vegetation cover refer to variations in the distribution, composition, and overall
structure of plant communities across different temporal and spatial scales. These changes can
occur natural.
132. “Autocomplete” is a software
function that provides
relevant suggestions based on
input by the user.
133. For this presentation, we’re
going to focus on an example
autocomplete associated with
searching for towns in
Australia.
134. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Label
135. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Input
136. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Clear mechanism
137. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Submit button
138. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Drop-down suggestions list
139. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Scroll bar (if needed)
140. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing autosuggest search component
Results area below
141. How do we make an
autocomplete widget
accessible?
142. Some of this is going to sound
awfully familiar…
145. 1. Use the TAB keystroke to
move focus into the search
input field from a previous
element with focus.
146. Search towns in Australia
Diagram showing input in focus
TAB
147. 2. Use the TAB keystroke to
move focus from the search
input to the “clear” button.
148. Search towns in Australia
Adaminaby, NSW
Diagram showing clear button in focus
TAB
149. 3. Use the ENTER keystroke to
trigger the “clear” button.
150. Search towns in Australia
Adaminaby, NSW
Diagram showing selected clear button
ENTER
151. Note: When the “clear” button
has been triggered, the search
input field should be cleared
and focus should shift to this
field again.
152. Search towns in Australia
Diagram showing focus move for clear button back to search input
153. 4. Use the TAB keystroke to
move focus from the clear
button to the submit button.
154. Adaminaby, NSW
Search towns in Australia
Diagram showing focus move form the clear button to the submit button
TAB
155. 5. Use the ENTER keystroke to
trigger the submit button.
156. Search towns in Australia
Adaminaby, NSW
Diagram showing selected submit button
ENTER
157. Note: When the submit button
has been triggered, focus
should shift to the first search
result below the autocomplete
search widget.
158. Search towns in Australia
Bell, NSW
Bell is a small rural and residential village in the
Blue Mountains region of New South Wales.
Bells Beach, VIC
Bells Beach is a coastal locality of Victoria,
Australia iand a renowned surf beach.
Bell
Diagram showing focus move from submit button to first search result
159. 6. Use the DOWN ARROW
keystroke to move focus from
the search input field to the
first item in list of
autocomplete suggestions.
160. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing focus move from input to first suggestion
DOWN ARROW
161. 7. Use the UP ARROW and DOWN
ARROW keystrokes to navigate
backwards and forwards
through suggestions.
162. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing second selection in focus and arrows to indicate focus can move backwards or forwards
DOWN ARROW
UP ARROW
163. 8: Users should not be able to
DOWN ARROW past the last
suggestion option.
164. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing last selection in focus and red cross to indicate focus cannot go forward
DOWN ARROW
165. 9. Some developers allow DOWN
ARROW keystrokes to loop from
the last suggestion directly
back to the initial input box.
166. However, I have found that
some users find this
confusing. They may not be
aware that they have returning
to the input field.
167. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing last selection in focus and red cross to indicate focus cannot jump to search input
DOWN ARROW
168. I prefer to follow the default
<select> behaviour where
focus loops through all
options only.
From last back to first etc.
169. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing last selection in focus and focus jumping to the first option
DOWN ARROW
170. 10. Use the ENTER keystrokes to
select an autocomplete
suggestion.
171. Search towns in Australia
ar
Arltunga, NT
Armadale, WA
Armidale, NSW
Arno Bay, SA
Diagram showing selected suggest option
ENTER
172. Note: When the ENTER
keystroke has been triggered,
focus should shift back to the
search input field.
173. Search towns in Australia
Armadale, WA
Diagram showing focus move from selected suggestion to search input field
174. 11. Use the ESC keystroke to
close the suggestion list and
return focus to the initial input
(i.e. if none of the suggestions
are relevant).
175. Search towns in Australia
ar
Diagram showing focus returning to input
ESC
198. More importantly, this native
“clear” button often cannot be
accessed via the TAB
keystroke, so it is inaccessible
for many Assistive Technology
users.
199. So, it is better to use a separate
<button> element for clearing
the field.
202. This points to a matching ID
value inside the hidden <div>
element below.
203. <label for="search">Search towns in Australia</label>
<input
id="search"
type="text"
aria-describedby="instructions"
>
<div id="instructions" aria-live="assertive"
style="display: none;">
When autocomplete options are available, use up and
down arrows to review and enter to select.
</div>
205. The aria-owns attribute
defines a “parent/child
contextual relationship to
assistive technologies that is
otherwise impossible to infer
from the DOM”.
206. In other words, we can define
the <input> element as the
parent, and the <ul> element
as the child element.
255. The aria-live attribute is set
to "assertive". This informs
assistive technologies as soon
as anything inside this element
is dynamically changed.