ADA - gettectonic.com - Page 14
web content accessibility guidelines
27Jun

Web Content Accessibility Guidelines

WCAG and ADA compliance While compliance with the Americans with Disabilities Act (ADA) and WCAG conformance have become almost synonymous over the years, it’s important to understand the distinction. Since WCAG itself is not a law, but a set of accessibility standards, there is no such thing as “compliance” with WCAG. However, WCAG was designed to help website owners achieve the level of accessibility that is required by laws like the ADA. It can be helpful to think of accessibility laws such as the ADA as the end destination—i.e., web accessibility for all—while WCAG maps out how to get there. Web content accessibility guidelines follow. Republished from www.w3.org Web Content Accessibility Guidelines Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general. WCAG 2.1 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. See Web Content Accessibility Guidelines (WCAG) Overview for an introduction and links to WCAG technical and educational material. WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [WCAG20], which was published as a W3C Recommendation December 2008. Content that conforms to WCAG 2.1 also conforms to WCAG 2.0. The WG intends that for policies requiring conformance to WCAG 2.0, WCAG 2.1 can provide an alternate means of conformance. The publication of WCAG 2.1 does not deprecate or supersede WCAG 2.0. While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 2.1 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating Web accessibility policies. Status of This Document This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/. This is a Recommendation of WCAG 2.1 by the Accessibility Guidelines Working Group. This incorporates errata and are described in the change log. At some point additional changes might be incorporated into an Edited or Amended Recommendation. To comment, file an issue in the W3C WCAG GitHub repository. Although the proposed Success Criteria in this document reference issues tracking discussion, the Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to [email protected] (comment archive). This document was published by the Accessibility Guidelines Working Group as a Recommendation using the Recommendation track. W3C recommends the wide deployment of this specification as a standard for the Web. A W3C Recommendation is a specification that, after extensive consensus-building, is endorsed by W3C and its Members, and has commitments from Working Group members to royalty-free licensing for implementations. This document was produced by a group operating under the 1 August 2017 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. This document is governed by the 12 June 2023 W3C Process Document. Requirements for WCAG 2.1 Introduction This section is non-normative. Background on WCAG 2 Web Content Accessibility Guidelines (WCAG) 2.1 defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees, and combinations of disability. These guidelines also make Web content more usable by older individuals with changing abilities due to aging and often improve usability for users in general. WCAG 2.1 is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals, organizations, and governments internationally. WCAG 2.1 builds on WCAG 2.0 [WCAG20], which in turn built on WCAG 1.0 [WAI-WEBCONTENT] and is designed to apply broadly to different Web technologies now and in the future, and to be testable with a combination of automated testing and human evaluation. For an introduction to WCAG, see the Web Content Accessibility Guidelines (WCAG) Overview. Significant challenges were encountered in defining additional criteria to address cognitive, language, and learning disabilities, including a short timeline for development as well as challenges in reaching consensus on testability, implementability, and international considerations of proposals. Work will carry on in this area in future versions of WCAG. We encourage authors to refer to our supplemental guidance on improving inclusion for people with disabilities, including learning and cognitive disabilities, people with low-vision, and more. Web accessibility depends not only on accessible content but also on accessible Web browsers and other user agents. Authoring tools also have an important role in Web accessibility. For an overview of how these components of Web development and interaction work together, see: Where this document refers to WCAG 2 it is intended to mean any and all versions of WCAG that start with 2. WCAG

Read More
June 27, 2023in Salesforce Sales Cloud
field dependencies
10Jul

Guide to Salesforce Field Dependencies

Salesforce provides robust tools to optimize processes, streamline workflows, and ensure data accuracy. In this guide, we’ll explore how to set up Salesforce field dependencies, implement validation rules, and use formula fields to enhance data quality and maintain data integrity across your organization. Understanding Field Dependency Field dependency in Salesforce allows you to filter and display relevant options in one picklist based on the user’s selection in another picklist. It links a controlling field and a dependent field, where the controlling field determines which values are shown in the dependent field. This helps maintain data integrity by preventing irrelevant selections, ensuring accurate and consistent data. Benefits of Field Dependencies Here’s why field dependencies are a valuable asset in Salesforce: Popular Use Cases for Field Dependencies How to Set Up Field Dependencies Best Practices for Managing Field Dependencies Conclusion Salesforce field dependencies are a powerful feature for ensuring clean data, enhancing workflows, and improving user experience. By enabling context-specific data entry, they reduce errors and save time, boosting productivity across your organization. If you need expert assistance with Salesforce configurations, Tectonic, a trusted Salesforce consultant, can help. With deep expertise in Salesforce solutions, Tectonic ensures your workflows are optimized and your Salesforce environment is perfectly aligned with your business needs. Reach out today to unlock the full potential of Salesforce for your organization. Content updated October 2024. Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Health Cloud Brings Healthcare Transformation Following swiftly after last week’s successful launch of Financial Services Cloud, Salesforce has announced the second installment in its series Read more

Read More
July 10, 2022in Data, Salesforce
Connected Culture
20Nov

Creating a Connected Workplace Culture

Creating a Connected Workplace Culture: Bridging the Physical and Digital Divide In today’s workplace, fostering genuine employee connection is no longer a luxury—it’s a critical business imperative. With the widespread adoption of remote and hybrid work models, organizations face mounting challenges in creating meaningful employee experiences and cultivating team cohesion. Yet, the need for connection has never been more urgent. The Cost of Disconnection Recent findings reveal a stark reality: over half of U.S. employees report feeling disconnected. This issue extends beyond personal dissatisfaction, becoming a crisis for organizations striving to attract, engage, and retain top talent. Employees who feel connected to their workplace culture are: The Challenge of Distance and Distraction Physical Separation Remote and hybrid work environments have minimized the spontaneous interactions and informal conversations that naturally foster camaraderie. This lack of face-to-face contact can lead to feelings of isolation and fragmented workplace cultures. Technology Overload At the same time, the explosion of workplace apps has created a disorganized digital landscape. With countless tools for HR, benefits, payroll, learning, and more, employees often struggle to navigate an overwhelming maze of applications. This fragmentation not only hinders productivity but also amplifies cognitive overload and decision fatigue, further diminishing the employee experience. So, how can organizations overcome these barriers and build a connected workplace culture in an age of physical distance and digital distractions? Building a Connected Workplace Strategy Connection doesn’t happen by chance. It requires deliberate planning, adaptability, and a deep understanding of the evolving workplace dynamic. Here’s how organizations can take intentional steps toward fostering meaningful connections: 1. Act with Purpose 2. Leverage the Right Tools 3. Prioritize Clear and Open Communication 4. Embrace Feedback 5. Commit to Continuous Improvement Moving Forward: Connection as a Competitive Advantage A connected workplace culture isn’t just about improving employee satisfaction—it’s a strategic advantage that drives engagement, productivity, and retention. By bridging the physical and digital divide with intentional actions and meaningful tools, organizations can foster stronger, more connected teams prepared to thrive in a modern, dynamic work environment. Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Health Cloud Brings Healthcare Transformation Following swiftly after last week’s successful launch of Financial Services Cloud, Salesforce has announced the second installment in its series Read more Top Ten Reasons Why Tectonic Loves the Cloud The Cloud is Good for Everyone – Why Tectonic loves the cloud You don’t need to worry about tracking licenses. Read more

Read More
November 20, 2021in Technology
Headless Commerce is the Future of E-Commerce
18Oct

Headless Commerce is the Future of E-Commerce

Why Headless Commerce is the Future of E-Commerce You’ve likely heard it said time and again: the future of e-commerce is headless. But why is this prediction so widespread? Why are 35% of businesses expected to adopt a headless architecture by 2025? high-code headless solutions and commerce-oriented analytics platforms come into play. Headless commerce is the future of e-commerce. Headless commerce refers to a system where the frontend of your website—encompassing the storefront and user experience—is decoupled from the backend, which handles data, functionality, and business logic. Recent statistics reveal that businesses adopting headless commerce have reduced time to market by 50%, increased site performance by 30%, and decreased the time spent on upgrades and bug fixes by 34%. Headless Commerce – Future of E-Commerce There are four key ways in which headless commerce enhances performance: 1. Personalization at Scale Headless architecture centralizes customer data and separates content creation from delivery, enabling businesses to personalize content and experiences more effectively across multiple touchpoints. 2. Greater Control Over Experiences Decoupling the frontend from the backend gives businesses full control over website functionality, performance, SEO, design, and layout. Changes can be made to the frontend without impacting backend systems, allowing for greater flexibility and responsiveness. 3. Enhanced Performance and Flexibility With smaller, more focused frontends, data loading becomes more efficient, resulting in faster site performance and optimized media. Headless architecture also allows for seamless integration with third-party systems, enabling businesses to adapt and evolve as needed. 4. Fostering a Culture of Experimentation The flexibility and control offered by headless commerce equip teams with the tools to experiment regularly and rigorously. This fosters a culture of experimentation, which can drive continuous improvement and innovation. While the first three benefits of headless commerce are valuable on their own, it’s the ability to support a culture of experimentation that truly sets headless apart. When these advantages come together, businesses can achieve a cumulative impact that significantly enhances their performance. Let’s explore how an experimental mindset can unlock the full potential of headless commerce. Nurturing a Culture of Experimentation with Headless Commerce The agility and efficiency of a headless approach empower e-commerce brands to build a culture centered on testing and optimizing customer experiences. However, experimentation inherently involves risk. Any new experience introduced to your website will affect its performance and user experience—ideally for the better, but there are no guarantees. The challenge, then, is how to mitigate those risks effectively. The good news is that a culture of experimentation and calculated risk-taking provides brands with continuous data-gathering opportunities, leading to better decision-making and improved outcomes. The key is ensuring that your business has complete data visibility. To minimize risks during testing and address potential issues quickly, you need full visibility into how every change impacts your site and customer experience. This allows your team to identify what’s working, troubleshoot what isn’t, and make informed decisions based on real-time insights. Rapid deployment of new experiences can then become a true competitive advantage, enabling you to leverage data-backed insights to enhance your digital offerings. Experimenting Safely with Headless Commerce To illustrate this, imagine a scenario where you’re A/B testing on your headless site. Suppose you discover that your checkout abandonment rate is higher than the industry average, and you hypothesize that a lengthy checkout process is to blame. You decide to run an A/B test comparing two versions of the checkout flow to see if a shorter process yields better results. However, deploying this test introduces an unexpected error in one variation, skewing your results. Without visibility into site errors, you might not even realize the issue, leading to confusing or inconclusive test outcomes. This is where high-code headless solutions and commerce-oriented analytics platforms come into play. They provide the necessary visibility and monitoring to support a culture of experimentation while minimizing risks. A platform like Noibu, a performance and error monitoring solution designed specifically for e-commerce, can help you navigate these challenges with agility. By continuously monitoring your site, Noibu detects any issues that arise during changes, alerts your team, and provides detailed technical insights to address the root cause quickly. This ensures that your experiments remain unaffected, allowing you to test freely without fearing conversion drops or revenue loss. This type of software acts as a safety net, promoting extensive experimentation by monitoring your site for potential errors and encouraging calculated risk-taking. Case Study: Ribble Cycles and the Benefits of Headless Commerce Ribble Cycles transitioned to a headless architecture and experienced greater freedom and control. Matthew Lawson, Chief Digital Officer, shares, “Choosing a headless/composable architecture for Ribble Cycles has given us unparalleled flexibility and control… [allowing] us to decouple the front end from backend services, enabling rapid iteration and unique, customer-centric features.” To mitigate the risks associated with site changes, Ribble Cycles turned to Noibu, an error-detection platform that allowed them to experiment and test solutions with reduced risk. “While headless brings risks, such as unforeseen impacts from changes, we mitigate these with advanced analytics and monitoring tools like Noibu,” Lawson notes. “These tools help us detect and resolve issues in real time, reinforcing a positive risk-taking culture and driving better results for our brand and customers.” With complete visibility into the impact of their experiments, Lawson’s team is now in control and reaping the rewards of their headless commerce strategy. “Best decision we have made,” adds Lawson. “We have a roadmap to take it even further.” Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Health Cloud Brings Healthcare Transformation Following swiftly after last week’s successful launch of Financial Services Cloud, Salesforce has announced the

Read More
October 18, 2021in Salesforce
Sensitive Information De-identification
02Feb

Sensitive Information De-identification

Using Google Cloud Data Loss Prevention with Salesforce for Sensitive Data Handling This insight discusses the transition from detecting and classifying sensitive data to preventing data loss using Google Cloud Data Loss Prevention (DLP). Sensitive Information De-identification for Salesforce is used as the data source to demonstrate how personal, health, credential, and financial information can be de-identified in unstructured data in near real-time. Overview of Google Cloud DLP Google Cloud DLP is a fully managed service designed to help discover, classify, and protect sensitive data. It easily transitions from detection to prevention by offering services that mask sensitive information and measure re-identification risk. Objective The goal was to demonstrate the ability to redact sensitive information in unstructured data at scale. Specifically, it aimed to determine whether sensitive data, such as credit card numbers, tax file numbers, and health care numbers, entered into Salesforce communications (Emails, Files, and Chatter) could be detected and redacted. Constraints Tested De-identifying Data with Google Cloud DLP API Instead of detailing the setup, this section focuses on the key areas of design. Google Design Decisions Supporting Disparate Data Sources with Multiple Integration Patterns and Redundant Design Salesforce Data Source De-identification targets include email addresses, Australian Medicare card numbers, GCP API keys, passwords, and credit card numbers. Credit card numbers are masked with asterisks, while other sensitive data is replaced with information types for readability (e.g., [email protected] becomes [redacted-email-address]). Sample Requests to Google De-identification Service JSON Structure to De-identify Text Using Google Cloud DLP API jsonCopy code{ // JSON structure } JSON Structure to De-identify Images Using Google Cloud DLP API jsonCopy code{ // JSON structure } Salesforce Design Decisions Redundancy and Batch Processing A scheduled batch job allows for recovery by polling unprocessed records. To handle large data volumes (e.g., 360,000 records over 5 days), the Salesforce BULK API is used to process queries and updates in large batch sizes, reducing the number of API calls. Sensitive Information De-identification Google Cloud Data Loss Prevention allows detecting and protecting assets with sensitive information, supporting a wide range of use cases across an enterprise. Proven Capabilities: Considerations and Lessons Learned Enhanced Email: Redacting tasks and EmailMessage records, handling read-only EmailMessage records by deleting and recreating them. Files: The architecture assumes files with sensitive data can be deleted and replaced with redacted versions. Audit Fields: Ensure setting CreatedDate and LastModifiedDate fields using original record dates. Field History Tracking: Avoid tracking fields intended for de-identification, tracking shadow fields instead. Image De-identification: Limited to JPEG, BMP, and PNG formats, with DOCX and PDF not yet supported. Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Health Cloud Brings Healthcare Transformation Following swiftly after last week’s successful launch of Financial Services Cloud, Salesforce has announced the second installment in its series Read more

Read More
February 2, 2021in Salesforce
Salesforce
24Apr

Salesforce Objects and Fields

Salesforce objects and fields are analogous to database tables and the table columns. Objects and fields structure your data. For example, the central object in the Salesforce data model represents accounts—companies and organizations involved with your business, such as customers, partners, and competitors. The term “record” describes a particular occurrence of an object (such as a specific account like “IBM” or “United Airlines” that is represented by an Account object). A record is analogous to a row in a database table. Objects already created for you by Salesforce are called standard objects. Objects that you create in your organization with the user interface or with the Metadata API are called custom objects. Objects you create that map to data stored outside your organization are called external objects. While this insight describes all of the objects available in the API, your applications work with only the objects that you are authorized to access. Programmatic access to objects is determined by the objects defined in your organization, your organization configuration, your user permissions and access settings (which are configured by your organization’s Salesforce admin), your data sharing model, and other factors related specifically to the object. Most of the objects accessible through the API are read-write objects. However, there are a few objects that are read-only. This fact is noted in the description for the object. For details about the data types and size restrictions for each object’s fields, see the Salesforce Field Reference Guide. Resources: Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Health Cloud Brings Healthcare Transformation Following swiftly after last week’s successful launch of Financial Services Cloud, Salesforce has announced the second installment in its series Read more

Read More
April 24, 2019in Data, Enterprise, Salesforce
Salesforce XML
26Mar

XML-Based Messaging Protocol

The primary focus of the XML based messaging Protocol Working Group is to establish a framework for XML-based messaging systems. This framework encompasses the specification of a message envelope format and a method for data serialization. While the emphasis is on RPC applications, the framework adheres to the specified principles, catering not exclusively but primarily to RPC applications. XML messaging represents a rapidly growing, dynamic area of IT, a situation that makes it exciting and tiresome at the same time. As B2B exchanges and other forms of inter-business electronic communication grow, XML messaging will be more widely deployed than ever. Dirk Reinshagen, Javaworld What are XML messages? XML Messaging format is designed to facilitate the exchange of structured information in the implementation of Web Services within computer networks. An XML interface serves as the foundational layer of a web services protocol stack, providing a fundamental messaging framework upon which web services can be constructed. How can XML text messages be read? XML files are encoded in plaintext, allowing them to be easily opened and read in any text editor. To do so, right-click the XML file and select “Open With.” A list of programs to open the file will appear, and you can choose “Notepad” (Windows) or “TextEdit” (Mac) for clear readability. SOAP API (Simple Object Access Protocol) is a protocol used for accessing web services in Salesforce. It enables developers to interact with the Salesforce platform using a standardized messaging format and receive data in the form of XML. is Like Related Posts Salesforce OEM AppExchange Expanding its reach beyond CRM, Salesforce.com has launched a new service called AppExchange OEM Edition, aimed at non-CRM service providers. Read more The Salesforce Story In Marc Benioff’s own words How did salesforce.com grow from a start up in a rented apartment into the world’s Read more Salesforce Jigsaw Salesforce.com, a prominent figure in cloud computing, has finalized a deal to acquire Jigsaw, a wiki-style business contact database, for Read more Health Cloud Brings Healthcare Transformation Following swiftly after last week’s successful launch of Financial Services Cloud, Salesforce has announced the second installment in its series Read more

Read More
March 26, 2019in Data, Salesforce

Subscribe to our mailing list. Join our mail list to receive our newsletter

We'll keep you up to date with our latest news, insights, free resources, and much more.
Don't worry, we won't spam you.
gettectonic.com