Today marks the 27th Anniversary of the Americans with Disabilities Act (ADA).  Unfortunately for businesses, two recent developments in the context of website accessibility suggest that there is no reason to celebrate and every reason to believe the ever-increasing wave of demand letters and lawsuits in this area will continue unabated.

First, in Lucia Marett v. Five Guys Enterprises LLC (Case No. 1:17-cv-00788-KBF), the U.S. District Court for the Southern District of New York has finally issued a decision directly speaking to the applicability of Title III of the ADA (Title III) to websites, denying Five Guys’ motion to dismiss, and holding that Title III does indeed apply to websites.  Facing a class action lawsuit brought by serial plaintiff, Lucia Marett, Five Guys sought to dismiss the claim that its website (which, among other things, allows customers to order food online for delivery or pick up at its brick and mortar stores) violated Title III and related state/local statutes because it is inaccessible to the blind, on the grounds that Title III does not apply to websites and, even if it did, the case was moot because Five Guys was in the process of updating its website to provide accessibility.  The Court rejected Five Guys’ arguments.  Citing both the text and the broad and sweeping purpose of the ADA, the Court held that Title III applies to websites – either as its own place of public accommodation or as a result of its close relationship as a service of Five Guys’ restaurants (which the court noted are indisputably public accommodations under Title III).  Further, the court was unmoved by Five Guys’ ongoing efforts to make its website accessible because they had yet to successfully do so and there was no absolutely clear assurance that further accessibility issues would be avoided.  The fact that the Court leaves open the possibility that a website conducting business only in cyber-space might have to comply with Title III is troubling as, to date, that position had remained an outlier, being only adopted by a couple of district courts.

Second, the Trump Administration has finally released its first Unified Regulatory Agenda and – in accordance with its goal of reducing the number of federal regulations – the private sector website accessibility regulations, most recently earmarked for 2018, have been marked as “Inactive.”  The potential for website accessibility regulations has long been one of the factors mitigating against website accessibility lawsuits.  With no reasonable expectation for such regulations in the near future, the courts will continue to serve as the primary forum for the development of this body of law.

These developments, taken in tandem with the recent post-trial verdict for Plaintiff’s in the Winn-Dixie litigation and the recent Hobby Lobby decision further devaluing various jurisdictional and due process defenses may create a perfect storm further emboldening an already aggressive plaintiff’s bar to continue to push website accessibility demands and lawsuits.  Indeed, in recent weeks we have not only seen another surge in the number of such actions being filed, but regular players in this space are using these decisions to push for greater settlement values, and new “copycat” players are starting to enter the fray.

Given the current climate, the best way for companies to try and avoid these litigations remains promptly taking legitimate and comprehensive steps to make their websites accessible.  This is particularly true for companies whose websites are tied to brick and mortar places of public accommodation but, now, may in some contexts and jurisdictions apply equally to cyber-only businesses.  Companies interested in taking such steps should conduct website accessibility audits (both user-based and code-based; and not simply running an automated scanning tool); add website accessibility obligations into vendor agreements; adopt and implement a website accessibility policy; and conduct training for necessary parties.  To the extent such efforts do not prompt plaintiffs to target other websites, they will certainly improve companies’ leverage for settlement negotiations and/or strategies for defending against litigations.

After years of ongoing and frequent developments on the website accessibility front, we now finally have – what is generally believed to be – the very first post-trial ADA verdict regarding website accessibility.  In deciding Juan Carlos Gil vs. Winn-Dixie Stores, Inc. (Civil Action No. 16-23020-Civ-Scola) – a matter in which Winn-Dixie first made an unsuccessful motion to dismiss the case (prompting the U.S. Department of Justice (“DOJ”) to file a Statement of Interest) – U.S. District Judge Robert N. Scola, Jr. of the Southern District of Florida issued a Verdict and Order ruling in favor of serial Plaintiff, Juan Carlos Gil, holding that Winn-Dixie violated Title III of the ADA (“Title III”) by not providing an accessible public website and, thus, not providing individuals with disabilities with “full and equal enjoyment.”

Judge Scola based his decision on the fact that Winn-Dixie’s website, “is heavily integrated with Winn-Dixie’s physical store locations” that are clearly places of public accommodation covered by Title III and, “operates as a gateway to the physical store locations” (e.g., by providing coupons and a store locator and allowing customers to refill prescriptions).  This line of reasoning follows the “nexus theory” body of law that has been developing over the past several years.  Based upon this conclusion, Winn-Dixie was ordered to: (i) bring its website into conformance with the WCAG 2.0 Guidelines; (ii) develop and adopt a website accessibility policy (publishing aspects of it upon the website); (iii) provide website accessibility training; (iv) conduct regular ongoing compliance audits; and (v) pay Plaintiff’s reasonable attorney’s fees and costs.  The parties were left to negotiate the exact timeframe for each requirement.

While this post-trial verdict does not have precedential value in other matters, it does raise a variety of points that businesses should consider as they continue to confront the still-increasing number of website accessibility demand letters and lawsuits:

  • The Court applied the nexus theory to the Winn-Dixie website even though customers could not make purchases directly through the website.  The Court deemed the ability to obtain coupons and link them to customer discount cards (for use in stores), refill prescriptions (for in-store pick up), and the presence of the store locator sufficient services for a nexus to exist between the brick and mortar locations and the website;
  • By applying the nexus theory, the Court was able to avoid having to rule on whether a website is a public accommodation in and of itself (a point of law courts remain split on);
  • The Court adopted the WCAG 2.0 Guidelines as the standard of website accessibility, thus following DOJ, the recently refreshed standards for Section 508 of the Rehabilitation Act, the Air Carrier Access Act, and countless private settlements between businesses and advocacy groups or private plaintiffs reached over the past 5 years;
  • The Court gave heavy weight to the testimony of an “accessibility consultant” who had conducted an audit of the Winn-Dixie site and testified very favorably for the Plaintiff that he did not believe that remediation process would be terribly difficult;
  • Relying upon the accessibility consultant’s representations, the Court went far beyond the scope of most existing website accessibility agreements by holding Winn-Dixie must require that any third-parties – including tech-giants such as Google – who are responsible for aspects of the website to also conform to the WCAG 2.0 while operating as part of the Winn-Dixie website;
  • The Court was unmoved by Winn-Dixie’s estimates that the remediation work to bring the website into conformance with WCAG 2.0 could cost upwards of two hundred and fifty thousand dollars ($250,000), and did not believe that such an amount would constitute an undue burden, noting that in the preceding 2 years the company had spent a total of approximately nine million dollars ($9,000,000) to launch a new website and then modify that new website to roll out a new customer rewards system; and, finally, in the one somewhat helpful piece for businesses;
  • The Court noted that in making a website accessible, a business need not ensure that it is accessible on all browsers and when read by all screen reader programs, provided that it is accessible on “main browsers” (e.g., Google Chrome, Internet Explorer, and Apple Safari) when read by “main screen reader programs” (e.g., JAWS and NVDA).

Given the Trump Administration’s edict against the promulgation of new regulations (without first eliminating multiple existing similar regulations) it is increasingly unlikely that DOJ will issue private sector website accessibility regulations in the near future.  Therefore, businesses can expect advocacy groups and private (often serial) plaintiffs to continue to threaten and/or bring website accessibility actions under both the ADA and corresponding state laws.  With that in mind, this verdict serves as a strong reminder of the risks of litigating a website accessibility matter, at least in situations where there is a reasonably clear nexus between a brick and mortar place of public accommodation and the website.

Internet Connectivity and Web Browser - AbstractOn April 28, 2016, the U.S. Department of Justice, Civil Rights Division, withdrew its Notice of Proposed Rulemaking (NPRM) titled Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities.  This original initiative, which was commenced at the 20th Anniversary of the ADA in 2010, was expected to result in a final NPRM setting forth website accessibility regulations for state and local government entities later this year.  Instead, citing a need to address the evolution and enhancement of technology (both with respect to web design and assistive technology for individuals with disabilities) and to collect more information on the costs and benefits associated with making websites accessible, DOJ “refreshed” its regulatory process and, instead, on May 9, 2016, published a Supplemental Notice of Proposed Rulemaking (SNPRM) in the federal register.

By August 8, 2016, the SNPRM seeks comments on a variety of issues, including, among others:

  • The appropriate technical standards for providing an accessible website (e.g., WCAG 2.0?);
  • The time period covered entities should be given for compliance once the regulations are effective (e.g., two years?)  and whether additional time should be granted for any specific requirements (e.g., narrative description?);
  • Whether exemptions should be granted for a variety of reasons (e.g., smaller entities; archived materials; existing pdf/Word documents; third-party content/links);
  • Should alternative formats ever be an acceptable alternative to an accessible website? and
  • Should mobile applications be covered by the regulations?

While this development does not directly impact businesses covered by Title III, it does suggest a few relevant considerations.  The questions posed in the SNPRM indicate that DOJ is considering many of the issues that Title III businesses have been forced to grapple with on their own in the face of the recent wave of website accessibility demand letters and lawsuits commenced on behalf of private plaintiffs and advocacy groups.  It would be a positive development for any eventual government regulations to clearly speak to these issues.  Conversely, it may be even longer before we see final regulations for Title III entities.  DOJ has long indicated its intent to first promulgate Title II regulations and then draw upon them in developing subsequent Title III regulations.  While the final Title II regulations were expected in 2016, the Title III regulations were already not expected until any earlier than 2018.  Therefore, this unexpected development could result in even further delays in the issuance of final Title III regulations (something which could also be impacted by any developments relating to this being an election year) resulting in businesses continuing to have to draw teachings from a variety of indirect/analogous resources when assessing how to best address accessible technology issues.

One Industry Takes Action

In the face of mounting frustration stemming from DOJ’s ongoing delays in promulgating website accessibility regulations while plaintiff’s counsel are allowed to continue to aggressively pursue claims some in the real estate industry recently decided to take action.  Citing “the growing confusion around web site accessibility,” on April 29, 2016, the National Association of Realtors wrote a letter to DOJ’s Civil Rights Division imploring DOJ to take actions to regulate the issue of website accessibility for Title III entities as soon as possible.  The letter highlighted the unfortunate dynamic that currently exists as DOJ and plaintiffs’ counsel seek to enforce broad overarching civil rights provisions in the absence of any uniform federal regulations.  (This is similar to the December 2015 efforts of Senator Edward J. Markey (D-Mass.) and a group of eight other Senators who wrote to the Obama administration calling for the prompt release of rules that would clarify and support access to information and communications technology ADA.)

Another Possible Approach to Mobile Accessibility?

While most current settlement agreements regarding website accessibility focus on desktop websites, many businesses are anticipating that the next target for plaintiffs and advocacy groups will be their mobile websites and applications.  Such concern is well founded as recent DOJ settlement agreements addressing accessible technology have included modifications to both desktop websites and mobile applications.

To date, those settlements have referenced the same compliance standard for both desktop and mobile websites and applications; WCAG 2.0 at Levels A and AA.  This is notwithstanding the fact that as currently written WCAG 2.0 does not directly incorporate mobile applications.  While the W3C has stated that a large number of existing WCAG 2.0 techniques can be applied to mobile content, a separate list of mobile-related guidelines is not currently available (though the W3C’s Mobile Accessibility Task Force is working to develop WCAG 2.0 Techniques that directly address emerging mobile accessibility challenges such as small screens, touch and gesture interface, and changing screen orientation for use with the WCAG).   In the interim, the W3C has published a working draft document titled “Mobile Accessibility:  How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile” that is intended to help mobile app developers apply the current WCAG 2.0 requirements to mobile applications.

However, a recent settlement between Netflix Inc. and the American Council of the Blind and Bay State Council of the Blind took a somewhat different approach.  While relying upon WCAG 2.0 Levels A and AA for the desktop website obligations, for mobile applicable devices, the agreement instead referenced the British Broadcasting Corporation’s Mobile Accessibility Standards and Guidelines version 1.0 (the “BBC Mobile Requirements”).

The BBC Mobile Requirements are a set of best practices for mobile web content and applications.  Instead of attempting to apply the desktop website requirements of the WCAG 2.0 to mobile applications, the BBC Mobile Requirements provide mobile application developers with a list of accessibility requirements for 11 topics that are specifically geared to enhance the accessibility of mobile applications.  The BBC Mobile Requirements were developed to:  (i) more accurately reflect the technology used by mobile applications; (ii) provide testing criteria that can be specifically applied to mobile devices; and (iii) provide developers of the two most pervasive mobile application platforms – iOS (Apple) and Android – with specific guidance for providing accessibility where one technique may not be applicable to both platforms.  They are categorized as:  (i) “Standards,” which are identified by the words, “Must” or “Must Not”; and (ii) “Guidelines,” which are identified by the words, “Should” or “Should Not.”  Per the BBC Mobile Requirements website, “In general, standards are best practices that can easily be tested with specific criteria that is not subjective and is technologically possible to achieve with current assistive technology on mobile devices.  Guidelines are less testable but considered core to accessible mobile website and apps.”

For the most part, the BBC Mobile Requirements reflect existing WCAG 2.0 requirements.  For example, the BBC Mobile Requirements state that mobile application content requiring user input (e.g., forms to sign up for email alerts) should have explicit labels describing the type of user input that is required.  This is similar to WCAG 2.0 Level A Guideline 3.3.2 – Labels or Instructions, requiring that, “Labels or instructions are provided when content requires user input.”  Additionally, in some instances, the BBC Mobile Requirements directly reference the WCAG 2.0.  For example, the BBC Mobile Requirements’ Standard for color contrast states that developers should “… use the WCAG 2.0 Level AA contrast ratio of at least 4.5:1.”  However, there are some BBC Mobile Requirements, such as “Touch target size” (requiring mobile application content to be structured so that it is large enough for a user to tap the target area comfortable with one finger), that do not have an equivalent WCAG 2.0 requirement at this time.

Given the challenges some businesses have cited in directly applying all WCAG 2.0 guidelines to certain aspects of mobile applications, the BBC Mobile Requirements offer another possible consideration.  However, the lack of clarity with respect to this issue only underscores why DOJ’s most recent additional regulatory delay is the sources of considerable frustration for most businesses.

As always, keep following EBG’s blogs for updates regarding ongoing developments in accessible technology.

While many continue to wait with growing impatience for the U.S. Department of Justice to finally issue regulations governing website accessibility for businesses under Title III of the ADA, DOJ has just launched a new online resource for those interested in staying abreast of developments in the overall area of accessible technology. 

This new site is meant to provide further guidance and information to employers, state/local governments, businesses and non-profits, and individuals with disabilities by serving as a “one stop” source for DOJ’s technical assistance and guidance about accessible technology (e.g., website accessibility, e-readers, point-of-sale devices), as well as providing up to date information about DOJ’s enforcement efforts, regulatory/rulemaking endeavors, and other related initiatives in this sphere. 

We will, of course, also continue to keep you apprised of breaking news in this rapidly developing area of the law. 

 

As I have discussed in many of my prior blog posts, over the past few years there has been a significant expansion in accessibility cases brought under Title III of the ADA (and related state and local accessibility statutes) with the focus of the litigations transitioning from brick and mortar issues to accessible technology.  As businesses continue to compete to provide customers and guests with more attractive services and amenities, we have seen increased utilization of technology to provide those enhanced experiences.  However, in adopting and increasingly relying on new technologies such as websites, mobile applications, and touchscreen technology (e.g., point of sale devices, beverage dispensers, check-in kiosks) accessibility is often overlooked because of the lack of specific federal standards in most contexts.  In turn, regulators, advocates, and ambitious plaintiff’s firms across the country have pursued actions in virtually all industries attacking the inaccessibility of various technology, under theories that inaccessible technology denies individuals with disabilities full and equal enjoyment of the offered goods/services/amenities and/or requires the business to provide access via auxiliary aids and services.  With the rise in accessible technology litigation, we are finally beginning to see greater guidance from the courts regarding the scope of businesses’ obligations in these contexts.  The two recent decisions discussed below– one in New York and the other in California – do just that.

Flexibility When Utilizing Touchscreen Technology In Certain Contexts

The recent ruling by the U.S. District Court for the Southern District of New York in West v. Moe’s Franchisor, LLC, provides businesses utilizing touchscreen technology to provide certain types of goods and services to its patrons with a possible roadmap for avoiding liability under Title III.  This litigation stemmed from Moe’s Restaurant installation of “Freestyle” drink dispensers that provide customers with the ability to select from over 100 distinct beverages using a touchscreen interface.  Plaintiffs, who are blind, could not utilize the dispensers and, after failing to secure assistance from an employee of the restaurant, needed to rely upon other customers for assistance with the device.  As a result of their experience, plaintiffs filed a class action lawsuit alleging that the inaccessibility of the touchscreen drink dispensers (the “Freestyle Dispensers”) violated Title III of the ADA and the New York State and New York City Human Rights Laws.  Specifically, plaintiffs alleged the Dispensers should have provided adaptive technology, such as tactile/Braille controls and a screen reader that provided audible instructions, as auxiliary aids and services.

In granting Moe’s motion to dismiss, the Court agreed with Moe’s argument it had appropriately met Title III’s obligation that places of public accommodation provide auxiliary aids and services to patrons with disabilities.  In meeting this flexible obligation, while the place of public accommodation is encouraged to consult with the individual with a disability, Title III leaves the ultimate determination of what auxiliary aid/service is appropriate up to the place of public accommodation provided the option adopted is effective.  The Court noted that one type of auxiliary aid/service expressly contemplated by Title III’s governing regulations is the provision of employees trained to read menus to guests who are blind.  To that end, the Court concluded that “nothing in the ADA or its implementing regulations supports Plaintiffs’ argument that Moe’s must alter its Freestyle machines in a way that allows blind individuals to retrieve beverages without assistance.”  While the Court conceded that providing accessible Freestyle Dispensers to enable independent usage by guests with disabilities might be feasible and/or preferable, because Moe’s trained its employees to provide assistance to guests with disabilities who had difficulties operating the Freestyle Dispensers, plaintiffs failed to establish a claim that Moe’s violated Title III or the equivalent state/city laws.  (The fact that in one instance Plaintiffs did not promptly obtain such assistance was insufficient to alter this conclusion.)

This decision, while only directly applicable to businesses in the SDNY’s jurisdiction, certainly provides support for the argument that even when adopting the use of accessible technology, a business may not always have to provide directly accessible technology in lieu of offering the prompt assistance of well-trained employees (and ideally indicating the availability of such assistance via accessible signage).  One important note of caution, however, in reaching its conclusion, the Court took care to distinguish that its decision might have been different if the technology being considered touched upon plaintiffs’ legitimate privacy concerns (e.g., a financial transaction).  Therefore, businesses should pause before seeking to apply the teachings of this decision to devices such as touchscreen point-of-sale/debit card technology (indeed, California has a state law expressly requiring accessible point-of-sale devices).

Website Accessibility Obligations Continue to Become More Certain

In a decision on the opposite end of the country last month that will not be met with the same reaction by businesses, the San Bernardino Superior Court in California held that a retailer violated the ADA (and the Unruh Act under California law) because its website was inaccessible to individuals who are blind or have low vision.  The decision in Davis v. BMI/BND Travelware, granting summary judgment to the plaintiff, is particularly noteworthy because prior decisions addressing the issue have occurred pre-discovery when considering motions to dismiss.

The Court, concluding that Plaintiff was denied full and equal enjoyment of the goods and services of defendant’s luggage business, based its decision that Title III applied to defendant’s website on the fact that the plaintiff demonstrated that he sought goods and services from a place of public accommodation and a sufficient nexus exists between defendant’s retail store and its website, which – by being inaccessible – directly impeded his ability to access defendant’s goods and services.  On the basis of this ruling, the Court ordered the defendant to: (i) either make its website “readily accessible to and usable by visually impaired individuals” or to terminate the website; and (ii) pay $4,000 in statutory damages under the Unruh Act on the grounds that, “the undisputed evidence is that plaintiff’s access to the website was prevented by the defendant at the time the website was designed.”  (However, the Court also refused to grant additional statutory damages for subsequent unsuccessful attempts to access the website.)

This decision reflects the latest in a series of rulings on website accessibility that increasingly reject arguments that business establishments with websites do not have an obligation under Title III and state/local laws to make the websites accessible.   Of course, as we’ve noted in the past, these decisions do not foreclose a variety of potentially successful defenses that may be asserted in later stages of a litigation – e.g., undue burden, fundamental alteration, and the provision of equivalent/alternative means of access.  As an increasing number of website accessibility cases proceed through litigation, businesses should soon have further guidance from the courts.  In the interim, the best way to guard against potential website accessibility claims continues to be to take prophylactic measures to address compliance before you receive a demand letter, complaint, or notice of investigation.

Joshua A. Stein
Joshua A. Stein

For businesses hoping to identify an avenue to quickly and definitively defeat the recent deluge of website accessibility claims brought by industrious plaintiff’s firms, advocacy groups, and government regulators in the initial stages of litigation, recent news out of the District of Massachusetts – rejecting technical/jurisdictional arguments raised by Harvard University and the Massachusetts Institute of Technology – provides the latest roadblock.

In National Association of the Deaf, et al., v. Harvard University, et al. (Case No. 3:15-cv-30023-MGM, Dist. Mass.) and National Association of the Deaf, et al., v. Massachusetts Institute of Technology (Case No. 3:15-cv-30024-MGM, Dist. Mass.), Plaintiffs brought claims on behalf of individuals who are deaf or hard-of-hearing, alleging that Harvard and MIT violated Section 504 of the Rehabilitation Act of 1973 and Title III of the Americans with Disabilities Act by failing to offer its online video content in a format accessible to individuals who are deaf or hard-of-hearing (e.g., by providing captioning).  Facing case law in the District of Massachusetts that already made arguing against the potential applicability of Title III to goods and services offered on websites more difficult (see Nat’l Assoc. of the Deaf v. Netflix, Inc. (D. Mass. June 19, 2012)), both Harvard and MIT made motions to dismiss and/or stay the actions pending the U.S. Department of Justice’s eventual promulgation of website accessibility regulations governing places of public accommodation under Title III (currently expected in 2018) by asserting the primary jurisdiction doctrine.  DOJ submitted Statements of Interest in both cases opposing Harvard and MIT’s motions, arguing that the courts are presently capable of adjudicating Plaintiffs’ claims based on the existing state of the law and any delay pending the release of its regulations would unduly prejudice the Plaintiffs.

While it will not become a final order until adopted by U.S. District Court Judge Mastrioanni, in an extensive and thorough decision, Magistrate Judge Robertson, denied both Harvard and MIT’s motions in their entirety.  The decisions hold, among other things, that these were not appropriate matters to invoke the primary jurisdiction doctrine because the existing law provides the necessary legal framework for the Court to appropriately adjudicate whether or not Section 504 and Title III were violated by Harvard and MIT’s failure to provide captioning of its online video content.  The Court explained that it did not need to await DOJ’s issuance of final regulations because, if necessary, it had other resources available through which to educate itself about any technical issues involved in the case.  Moreover, as the analysis involved in accessibility cases must be specifically tailored to the entity and situation in question, the Court was not concerned about the potential impact these decisions might have on any broader issues addressed by DOJ’s regulations.  Finally, noting that DOJ’s Title III regulations will not even be in final form if delivered as planned in 2018, the Court expressed concern about the amount of time that would elapse for Plaintiffs if it was concluded that the defendants were violating the law.  This decision comes on the heels of the U.S. District Court of the Western District of Pennsylvania’s decision this past November denying a similar motion to dismiss made by Huntington National Bank in defending against a claim brought by the law firm Carlson Lynch Sweet & Kilpea on behalf of Michelle Sipe.  (Sipe v. Huntington National Bank, Case No. 2:15-cv-01083-AJS (W.D.Pa. 2015))  While that decision came without any discussion, the papers filed by both parties relied heavily upon those submitted by the parties in the Harvard and MIT decisions.

These recent decisions reveal a reluctance among the courts to dismiss website accessibility actions on technical/jurisdictional grounds.  Taken along with the expanding number of jurisdictions who subscribe to legal theories accepting that Title III covers website accessibility (whether adopting a nexus theory or broadly interpreting the spirit and purpose of the ADA) and it is becoming increasingly clear that many businesses will have a difficult time ridding themselves of website accessibility claims in the early stages of litigation.  Of course, these decisions have been quick to note they do not foreclose a variety of potentially successful defenses that may be asserted later in the litigation – e.g., undue burden, fundamental alteration, and the provision of equivalent/alternative means of access.  While, to date, the existing website accessibility case law has not focused on when these defenses might prevail, with the recent proliferation of website accessibility demand letters and litigation, businesses should soon find themselves with greater guidance from the courts.  In the interim, the best way to guard against potential website accessibility claims continues to be to take prophylactic measures to address compliance before you receive a demand letter, complaint, or notice of investigation.

We will, of course, continue to monitor these ongoing developments and update you as appropriate.